This affects swamp serve's OAuth admission bootstrap (the device-flow client registration and --admins/--allowed-collectives resolution that run on swamp serve --auth-mode oauth).

On first run, serve does a device-flow client registration against the OAuth provider (default swamp-club.com), then uses the token from that flow to resolve --admins/--allowed-collectives values into concrete accounts. If that resolution fails — e.g. an --admins value doesn't match a real account — the process exits fatally, and the access token obtained during the device flow is never persisted anywhere. Every subsequent run reuses the already-stored client credentials but has no access token, and fails differently: "Cannot resolve usernames — no access token and no cached resolutions." The only way forward is to delete the stored client credentials (swamp vault delete local-secrets oauth-client-id) and redo the entire device-flow browser confirmation from scratch, even though the client itself had already registered successfully.

A compounding factor: the --admins flag's help text example (user:oauth|user-123) doesn't match actual resolver behavior. The resolver strips the user: prefix and looks up the remainder as a literal swamp-club username via the directory API — so user:oauth|<subject-id> fails with "Username 'oauth|' not found," while the working form appears to be user:<username> (e.g. user:dmc). That makes it easy to supply an invalid value on the very first attempt, which is exactly when the token-loss bug above bites hardest.

Consequence observed: repeated invalid-value attempts under this flow drove three full device-flow registrations in about six minutes, which then triggered a 400 Bad Request from the device-authorization endpoint itself (apparent rate limiting). A confusing flag format can cascade into a "can't test this at all for a while" state.

Expected fix approach

Persist the access token (or at least the resolved admin/collective set) as soon as it's obtained during the device flow, before attempting to resolve --admins/--allowed-collectives — so a resolution failure doesn't discard already-valid credentials and force full re-registration. Separately, fix the --admins help text example to match actual behavior, or support the documented user:oauth|<subject-id> form if that was the original intent.

Steps to reproduce

swamp serve --auth-mode oauth --allowed-collectives <collective> --admins "user:oauth|<a-real-account-id>"
Complete the printed device-flow URL/code in a browser.
Observe: client registers successfully, then the process exits with Failed to resolve admin 'user:oauth|<id>': Username 'oauth|<id>' not found on <provider>.
Re-run the same command (client credentials are now cached from step 2).
Observe: immediately fails with Cannot resolve usernames — no access token and no cached resolutions. Clear stored credentials to re-register: swamp vault delete local-secrets oauth-client-id — even though a client was already registered and a token was briefly held during step 2/3.
Run swamp vault delete local-secrets oauth-client-id, retry with a corrected --admins "user:<username>" value — this requires a full new device-flow browser confirmation rather than reusing anything from the first attempt.

Environment

swamp 20260718.233837.0-sha.f5bb6b99 — bug reproduced on this build (three times, with different --admins values, across a fresh laptop session).
Not re-verified against the current 20260720.234931.0-sha.4770b0fd — the device-authorization rate limit encountered mid-testing made another live device-flow round-trip impractical at the time of filing.
OAuth provider: default (https://swamp-club.com).
--auth-mode oauth, --allowed-collectives, --admins all involved.

02Bog Flow

Shipped

7/24/2026, 5:59:06 PM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack727/24/2026, 4:42:10 PM

stack72 commented 7/24/2026, 5:59:17 PM

Thanks @dmc for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

worker daemon enable: relative/missing --cache-dir fails launchd EX_CONFIG while daemon status reports running

vault extensions: emit OTel spans for vault operations (AWS SM, Azure KV, 1Password)

azure-kv error wrapping loses original error type — ERROR_TYPE always 'Error' in traces

aws-sm deleteAnnotation removes all non-aws: tags, not just swamp-specific ones

Docs: document datastore directory relocation during setup

--quiet mode does not suppress in-process extension logger output

Expose resource attributes in DataHandle for workflow report stepExecutions

Expose workflow inputs in WorkflowReportContext

Issue redactor corrupts reports: dotted code identifiers masked as hostnames, loopback and RFC 5737 documentation IPs masked, angle-bracket placeholders half-eaten

data prune resolves auto-definitions at the local path, not the datastore path — deletes live models' data (verified: destroyed a working server token and an active grant)

workflow/job-lifetime data is never reclaimed — expiry check requires an ownerDefinition.workflowId that step execution never sets

runModel breadth limit (MAX_INVOCATION_BREADTH=100) is never enforced — tracking object is never written back to the caller context; verified 150/150 calls succeeded

serve daemon enable is ungated — it reports success, then the account gate fires inside the detached daemon, which crash-loops invisibly

Purely local operations require a swamp-club account: local-token serve is gated while deprecated --auth-mode none is not, third-party OIDC is gated, and 'Local_Encryption' is paywalled by capitalization

A collective token stored in auth.json (rather than SWAMP_API_KEY) is permanently scope-less — resolution only runs for the env var, and scopes are never persisted for collective tokens

An empty stored apiKey counts as authenticated — saveIdentityCache writes apiKey:'' on a virgin machine, permanently satisfying the mandatory-account gate with no credential

Account/scope gates fire before argument, type and repo validation — 'swamp vault create env my-vault' (the command's own example, an invalid type) returns a paywall instead of 'Unknown vault type'

auth token create advertises a 'collective:write' scope that does not exist, and following its advice hits 'collective tokens cannot create other collective tokens'

requireScope does exact string matching — fine-grained scopes fail gates that demand the literal wildcard, and minted scopes are never validated or normalized

Collective-token scope cache never expires, is never refreshed by whoami, and cannot be cleared via the CLI — scope changes and revocations never take effect

Collective-token scope cache is keyed on a 12-char token prefix — only 2 chars distinguish org tokens, so a rotated token silently inherits another token's scopes

Misleading 'Your collective token lacks the X scope' when scope resolution failed — startup whoami errors are silently swallowed

Community points / reputation: award points for upvoting extensions, feature requests, comments, and feed posts

globalArgs fields leak into method arguments when a method's arguments schema is a bare z.record()

swamp serve --auth-mode oauth: crash during first-run admin resolution discards the OAuth token, forcing full device-flow re-registration

Docs: document extension runtime permissions and device I/O workaround in user manual

datastore setup extension drops 'namespace' from --config, making extensions that require it impossible to configure

Kiro CLI v3 permissions: no capability covers disclose_context (skill loading)

CLI: swamp invite <email> to drive the platform-invite API

api-key-scoping explanation doc contradicts shipped fine-grained scopes

Fine-grained scopes for swamp.club access tokens

End-to-end UAT for fine-grained collective token scopes (#960)

Docs: document swamp auth token create command for collective tokens

open method fails for password-auth hosts: SSHPASS env set but ssh call never wrapped in sshpass

docs: update swamp skills for setup extension --namespace

apps sync/lookup fail with 'partial() cannot be used on object schemas containing refinements'

Docs: update autoGc documentation to reflect write-time version pruning

model search/list doesn't enumerate auto-created definitions under .swamp/auto-definitions/

CLI command to create scoped collective tokens (phase 8 of #960)

docs: document auth gates for team features (datastores, vaults, serve)

`datastore setup filesystem` never transfers content when leaving a sync-based (remote) datastore — copies only the catalog and hardcodes `filesPulled: 0`

Workflow/CLI output uses red text for non-error/informational lines, contradicting standard error-color convention

Support end-user timezones on https://swamp-club.com/u/shelson/activity

Document doctor datastores --repair for namespace contamination cleanup

version-drift check (from #236) is a raw string-inequality, false-positives on multi-model manifests and metadata-only bumps

Pre-flight checks receive unresolved vault.get() expression text, not the resolved secret

Invite people who have never used swamp to a collective (email invite flow)

docs: update giga-swamp manual pages for setup extension --namespace

Docs: update extension push output examples to include channel and visibility

Collective management API for extension-based automation

Remote --server wss:// fails through an HTTP/2 TLS reverse proxy (WS client ALPN is h2-only)

uat: add namespace isolation and shard resilience test coverage

docs: update giga-swamp guides and skills for setup extension --namespace

Quest page: all leaderboard usernames show 'Swamp Baby' title

Website extension search ignores API relevance — exact name match "good-planning" ranks #10 (API ranks it #1)

Extension/type search at method granularity — find capabilities, not just packages

data query and data get return the same payload under different keys

forEach leaves self.* unresolved in target

It is possible for a member to be a member of a collective twice

swamp-club: score-reads tierTotals GET overflows URL with inline param_ownerIds (Invalid URL, mislabeled clickhouse-network-error) for large collectives

Docker-related model types/workflows would benefit from first-class dry-run/plan support

Hide enterprise (SSO) operatives from announcements and leaderboard by default

Worker queries need a safe connected-worker filter for fleet fan-out

Published extension scores dependency-trust as "missing" (0/2) while client `extension quality` earns it (2/2); no verdict exposed

Add a :micdrop: emoji / reaction shortcode (swamp-native art included)

namespace unset --migrate silently deletes artifact history via catalog-rebuild GC (~484k files lost)

serve: workflow.approvals and workflow.run.search still full-scan the workflow-run store after the #1284 data.query pushdown

Bugs filed by a team-subscription user are not tagged "team" in the Lab

Bundled extension model cannot deserialize AWS SDK S3 XML that works in direct Deno

gcp/sheets spreadsheets-values: batch_get crashes with "Request with GET/HEAD method cannot have body"

Token creation API and UI scope selector for collective tokens (phase 4 of #960)

Make Cloudflare CRUD methods factory-aware so list-discovered resources can be managed in-place

[sc] quest-grant Mongo ops (recentHeartbeat/signalCounts/countIssueShipped) regressed to ~5s timeouts — missing index

Add @swamp/kubernetes/statefulset model type

Sync guard skips bound namespace directory during push — 0 files pushed after namespace migrate

Flaky #1052 preparePush test: mtime-granularity race on Linux tmpfs

command/shell renders JSON-object stdout lines as the literal string 'undefined'

Issue redactor treats the MongoDB authSource parameter as a secret, corrupting reproduction steps

Docs: document repo root resolution from subdirectories

Expose the swamp.club feed as an RSS feed

Grant revoke is never applied to the running server — under `--grant-reload auto` and `manual` alike, a revoked grant stays in force until an explicit `access reload`