swamp access token mint no longer prints the plaintext (per the swamp-club#1466 change noted in #1472). Instead it prints a retrieval hint — but that hint is not a valid command, so the token it just minted cannot be retrieved by following its own instructions.

Minting emits:

Vault: serve-local (key server-token-swamp-ui)

Retrieve the token with: swamp vault get serve-local server-token-swamp-ui

Running exactly that:

Error: Unexpected argument: server-token-swamp-ui

Usage: swamp vault get <vault_name_or_id>

To retrieve a secret value, use: swamp vault read-secret <vault_name> <key>

vault get takes only a vault name. The correct command is vault read-secret (added in #238).

Steps to reproduce

swamp vault create local_encryption serve-local
swamp access token mint swamp-ui --principal user:sntxrr --duration 365d --vault serve-local
Copy the Retrieve the token with: line verbatim and run it
It fails with Unexpected argument

Two follow-on papercuts on the same path

Both were hit immediately after correcting the command, so a fixed hint would ideally cover them:

read-secret refuses to run non-interactively without --yes: Error: stdin is not a terminal — use --yes (-y) to skip confirmation prompts non-interactively. Any scripted retrieval (CI, entrypoint, deploy script) needs --yes, which the hint would not tell you. Compare #1290, which standardised --yes.
The vault stores only the secret half, not the wire format. read-secret returns a bare 64-char secret, but serve expects <name>.<secret>. So even after finding the right command, passing the retrieved value straight to a client fails to authenticate, with no hint that the token name must be prepended. The mint output shows Token: swamp-ui and the vault key separately, but never states that the client format is the concatenation.

Suggested fix

Emit the working command, e.g.:

Retrieve the token with: swamp vault read-secret serve-local server-token-swamp-ui --yes
The client token is <name>.<secret> — prepend the token name: swamp-ui.<secret>

Impact

This is the documented headless path. The container case is exactly where the plaintext cannot be recovered any other way — it was never displayed — so a wrong hint means the operator has a minted, active token they cannot use, and the natural next guess (re-mint) leaves a second live token behind.

Environment

swamp 20260806.001601.0-sha.5bfddaa2 (also reproduced on 20260805.130625.0-sha.4e45e221)
swamp serve --auth-mode token, running in a Debian container
Vault type: local_encryption

#1472 — docs bug for the same change; it describes the emitted swamp vault get hint as the expected new behaviour, so this one is the hint itself being wrong rather than a duplicate
#238 — added vault read-secret
#1290 — --yes as the standard non-interactive confirmation flag

02Bog Flow

Shipped

8/7/2026, 3:06:31 AM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack728/7/2026, 2:19:51 AM

stack72 commented 8/7/2026, 3:06:40 AM

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

git: add pull, fetch --tags, and cherry-pick methods

Skill docs use invalid two-argument 'vault get' form

access token mint prints an invalid retrieval command (vault get, not vault read-secret)

serve reload and model edit timeout over --server in Kubernetes

Show user:<name> instead of user:<id> in grant list output

swamp auth whoami should report paid tier and trial status

Exclude swamp internal model types from model list output

Use whoami entitlement to explain private-extension push refusals

Document --restricted-commands flag for swamp serve

vault put: pass tags through to extension provider CreateSecret/setSecret calls

Docs: update manual for 23 new --server commands

Update VaultProvider interface in @systeminit/swamp-testing to support optional tags in put()

Docs: document --grants-file flag for swamp serve

Docs: document --server support for serve reload

Docs: add --tag flag to vault put reference

Docs: update manual for --detach-runs deprecation and HA auto-detection

Document the Codex plugin in swamp docs

Add --server support to CLI commands missing it

Document the swamp Claude Code plugin in the swamp documentation

Make --server a global CLI option

Add --server support to model cancel (server-side run cancellation)

Load grants from external source on swamp serve startup

swamp vault put should support tags for secret governance

Improve hot reload of the deamon, include extension source/bundle changes

Authenticated users must re-login after swamp serve restart

Add --server support to serve reload

Harden queue claim semantics: atomic claims + status-guarded markDelivered/markFailed across app queues

Auto-detect HA mode and deprecate --detach-runs flag

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

Resend newsletter audience sync: contacts, segments, backfill, unsubscribe sync-back

Move per-login token secrets from vault to encrypted control-plane store

Docs: document macOS TLS trust limitation and SSL_CERT_FILE workaround

Validate swamp serve deployment stack on startup

Docs: serve config file (.swamp/serve.yaml) and --config flag

Serve config file — read swamp serve configuration from YAML

Deno runtime does not trust ISRG Root YR — extensions fail with valid Let's Encrypt certs

Docs: update hot-reload reference to include trust list refresh

Cross-instance client re-attach for multi-instance swamp serve

vercel codegen: inline rawSyncResult in non-unwrap sync path

vercel codegen: unused listAll import blocks extension publish for 4 models

vercel codegen: add round-trip idempotency test for the pipeline

Operatives button on Collectives page does nothing

Track active runs in the control-plane store for cross-instance visibility

validateGlobalArgInputRefs checks step-level inputs but step schema rejects 'inputs' key

Docs: document continuous reconciliation and multi-instance serve flags

Docs: update workflow guard skip output to include guardExpression and guardResult

Make it aware hot reload on the deamon does not take into account trust list changes, or do take into account the trust list for the hot reload.

workflow validate: new 'GlobalArgument input references' check resolves model-definition ${{ inputs.* }} against workflow inputs, false-failing steps that supply the input

Continuous reconciliation for multi-instance swamp serve

Split the score-read circuit breaker so leaderboard pressure can't blank profile scores

oauth_sign_in telemetry records provider as the literal ":id" for every event

Ghost profile bypasses the score-read seam and 500s on a slow ledger

Profile score section blocks the render on a ClickHouse read

Council: set the scoring balance — command tiers, farm-decay parameters, cross-category ratio

Scoring coverage gaps: instrument drop-off, score ripples/mentions, reward invite-converts

Push down the two cheap leaderboard scans: ghost-gate dictionary and eventCounts owner filter

Materialize an active-days-by-id table for the streak board

score-rollup-projector: O(all-time ledger) closure + per-pod fan-out saturates prod ClickHouse CPU

Startup cache hydration for swamp serve instance replacement

Output a log line for steps skipped due to guards

extension quality scorer misreads a template-literal import specifier in generated code as an unresolvable bare import, hard-erroring the whole extension as UNSCORABLE

Add @swamp/kubernetes/statefulset model type

Docs: access token commands reference says plaintext is 'shown once'

Document --restricted-model-types flag for swamp serve

swamp auth server-login ignores SWAMP_SERVE_URL

s3-datastore extension: pullChanged writes namespace-stripped paths to local cache

serve oauth: an unrecognized device-token error kills the whole serve process instead of the bootstrap

s3-datastore: bidirectional sync pull writes namespace-stripped copies to cache root, wedging push with no supported recovery

CLI reports 'HTTP/2 not supported by this client' when the server actually returned 401 — masks auth failures as a transport error

access token mint: allow reusing a revoked token name

extension quality --json exits 1 with 'rubric factors missing' even when a full score was computed (unearned factor, not uncomputable)

serve oauth: startDeviceGrant discards the OAuth error field, making device-code failures undiagnosable

access token rotate: add --vault flag to override inherited vault

Extensions without a repository can't receive issues — including the issue asking them to add one

serve oauth bootstrap: device flow rate-limited to a 45-second window by validateClient counter, shared globally across tenants

workflow edit: after saving an invalid workflow, re-running edit reports "Workflow not found"

Authentication via Google Broken

Plus-addressed emails stripped on invite acceptance, breaking collective join and quest reward

Profile edit broken on Safari

Configurable write paths for object-creating commands (repo-relative swamp root)