swamp.club access tokens currently appear to have a broad account-level scope. This makes it hard to use tokens safely in automation/CI because a token intended only for extension publishing may also be able to perform unrelated sensitive actions.

Desired capability

When creating an access token, allow selecting fine-grained permissions/scopes. For example, I want to create a token that can publish extensions, but cannot:

change my user profile
yank/unyank/hide extensions
link or unlink accounts
perform other account-management actions

Proposed solution

Add scoped access tokens with explicit capabilities, such as:

extensions:publish
extensions:yank
extensions:unyank
extensions:hide
profile:write
accounts:link

The token creation UI/API/CLI should let users choose the minimal required permissions, and the registry/API should enforce those scopes on every authenticated action.

Why this matters

This would follow least-privilege principles and make it safer to store swamp.club tokens in CI/CD systems, especially for publishing extensions, without granting broad account control.

02Bog Flow

Shipped

7/24/2026, 12:35:35 AM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack727/14/2026, 6:19:19 PM

stack72 commented 7/24/2026, 12:34:40 AM

Shipped: fine-grained scopes for collective API tokens

This has been implemented across 8 PRs spanning both the swamp-club web app and the swamp CLI.

What was built

Scope system:

22 scopes across 10 resource categories: extensions (push, promote, read, wildcard), lab, profile, collective, billing, feed, notifications, oauth, serve, datastore, and vault
Wildcard expansion — extensions:* grants all fine-grained extension scopes
Legacy token detection — existing tokens default to extensions:* and show a "LEGACY — ROTATE" warning badge in the UI

Enforcement:

Server-side requireScope() guard on all collective-token-accessible routes (push, confirm, promote, search)
Clear 403 messages naming the missing scope
Infrastructure scopes (serve:*, datastore:*, vault:*) enforced at CLI command level for team features

Token creation:

Web UI scope selector at /o/[slug]/settings with grouped checkboxes (Extensions + Infrastructure)
API accepts optional scopes parameter on POST /api/v1/collectives/[slug]/api-tokens
CLI command: swamp auth token create --collective <slug> --scopes extensions:push,serve:*

CLI support:

Full collective token support — swamp auth whoami shows scopes, swamp extension push works with collective tokens
Scope-aware error messages on 403s

Introspection:

GET /api/whoami returns scopes for collective tokens
swamp auth whoami displays granted scopes

What this enables

CI pipelines can now create a token with only extensions:push and nothing else. That token can publish extensions but cannot promote, search private extensions, or perform any infrastructure operations. This is the least-privilege model requested in the issue.

Infrastructure tokens (serve:*, datastore:*, vault:*) authenticate team services with swamp-club.com, gating swamp serve, remote datastore setup, and non-local vault creation behind collective membership.

Remaining

#1374 — one explanation doc page still argues against fine-grained scopes and needs rewriting
#1375 — end-to-end UAT checklist
Personal API key scopes are a separate future track (different implementation path via BetterAuth)

stack72 commented 7/24/2026, 12:36:40 AM

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

Improve multi-word search query handling and guidance

swamp command doesn't check cwd

swamp auth login process fails when run remotely

serve boot OOM: findAllGlobalSince loads all workflow runs as full aggregates during reconciliation

extension search: channel-filtered results carry null version fields, and multiple --channel values collapse instead of unioning

s3-datastore: localHasAllRemoteEntries uses bare rel instead of localRelPath, always returns false in namespaced mode

datastoreSetupExtension migrates .swamp/ to cache root instead of namespace directory

swamp serve writes outputs/ outside the bound namespace — silently never persisted to the remote datastore

s3-datastore: bulk pull writes to cache root instead of the namespace, wedging push and arming a full-datastore delete

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

Workflow runs with wide dataArtifact fan-out (~400/run) OOM both workflow history get and swamp serve boot, crash-looping the scheduler; rollback doesn't help (state-triggered, not release-triggered)

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

Reusable long-lived invite link: one URL to bring people into the swamp

Exclude swamp internal model types from model list output

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

swamp auth whoami should report paid tier and trial status

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