When swamp serve restarts (upgrade, crash recovery, instance replacement), all authenticated users must re-authenticate. Their existing tokens/sessions are invalidated because the server state that validated them is lost.

This breaks the seamless restart experience that the HA work delivers — pending runs are replayed, interrupted workflows are reconciled, but the user is kicked out and has to re-login before they can interact with the server again.

Steps to reproduce

Start swamp serve with --auth-mode token or --auth-mode oauth
Authenticate via swamp auth login --server
Run a command: swamp workflow search --server (works)
Restart serve (kill -TERM, then start again)
Run the same command: swamp workflow search --server
Authentication fails — user must re-login

Expected behavior

After serve restarts, previously authenticated users can continue using the server without re-authenticating. Their credentials should survive the restart.

Analysis

The issue depends on the auth mode:

Token auth (--auth-mode token)

Server tokens are minted via swamp/server-token model and stored as swamp data. The token secret was recently moved to the encrypted control-plane store (#1511). The token data record (name, state, bindings) is in the datastore.

On restart, the server should be able to re-validate tokens from the datastore — the token name and secret are durable. The issue may be that the server-token model's in-memory state isn't rehydrated on restart, or that the vault/control-plane store read path isn't exercised during token validation on a fresh process.

OAuth auth (--auth-mode oauth)

OAuth-minted tokens go through the device authorization flow, which mints a swamp/server-token. The flow stores:

OAuth client credentials in the vault (oauth-client-id, oauth-client-secret)
The minted server token in the datastore + encrypted secret in control-plane store
Collective snapshots on the token record

After restart, the same analysis as token auth applies — the token should be re-validatable from durable state.

Client-side credential storage

The CLI stores server credentials in ~/.config/swamp/servers.json via ServerCredentialRepository. These survive serve restarts — the client still has its token. The question is whether the server can still validate it.

What needs to happen

Investigate: on a fresh serve process, does authenticateServerToken successfully validate a token that was minted by the previous process? If not, what state is missing?
The token secret is in the encrypted control-plane store — does the new process read the encryption key and decrypt successfully?
The token data record (swamp/server-token model) is in the datastore — is it loaded on startup before the first authentication attempt?
Fix whatever gap prevents re-validation so that tokens survive restart seamlessly.

Impact

This affects every authenticated deployment. The HA system handles everything else seamlessly on restart — runs recover, pending work replays, heartbeats re-register. But the user has to re-login, which breaks the "zero-disruption restart" promise.

02Bog Flow

Shipped

8/5/2026, 3:03:33 AM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack728/5/2026, 1:09:50 AM

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)

Docs: document rollbackOnFailure with safety guidance for external-dependency models

Remote execution tutorial: sample runner output is missing the stdout line that #1462 restored

seadex-latent-bugs: latent product bugs pinned by the wave-2b test backfill

Remote step stdout is not streamed to the workflow runner (log artifact is transferred correctly)

Redactor false positives: HH:MM:SS timestamps masked as IPs, SHA-256 digests masked as secrets (both inside code fences)

Remote execution tutorial: worker token list output and inline workflow-summary block no longer match CLI output

Add rollbackOnFailure for method-level write atomicity

docs: working-with-data tutorial uses removed depends_on step key, blocking the tutorial