The CLI has a dedicated swamp issue security path for vulnerability reports, but ordinary bug and feature reports do not expose a documented way to mark the issue as confidential at creation time.

Expected behavior

Provide an option to create bug or feature issues with confidential visibility, for example swamp issue bug --confidential or swamp issue feature --confidential. Security issues should remain confidential by default, but non-security issues should be able to opt in to confidential handling when they contain private data (they mostly should not, but it can happen)

Why this matters

Some reports require private data to be useful, such as internal identifiers, private repository names, customer-specific details, logs, paths, or reproduction context. Users may avoid including enough information to diagnose the problem because they do not want to leak private information publicly. A confidential option would let them provide actionable details safely without mislabeling the report as a security vulnerability.

Suggested behavior

swamp issue security remains confidential by default.
swamp issue bug and swamp issue feature remain public/non-confidential by default.
Bug and feature reports can opt in to confidential visibility.
The CLI should make the visibility clear before submission and in JSON output.

02Bog Flow

Closed

7/8/2026, 11:40:42 PM

No activity in this phase yet.

03Sludge Pulse

stack72 commented 7/8/2026, 11:40:42 PM

@evrardjp Thanks for raising this — it's a real concern and we've taken a different approach to solve the underlying problem.

Rather than adding --confidential visibility, we've implemented automatic client-side redaction of identifying information before issue content ever leaves the machine. This means sensitive data never reaches the server in the first place, which is a stronger guarantee than access controls.

When you run swamp issue bug (or feature/security/ripple/edit), the CLI now automatically scrubs:

Credentials, tokens, API keys, passwords
Email addresses, phone numbers, SSNs, credit cards
IP addresses → stable placeholders like [IP-1], [IP-2]
Hostnames/FQDNs → stable placeholders like [HOST-1], [HOST-2] (public hosts like github.com are preserved)
Home directory usernames → /Users/[REDACTED]/...
Connection string passwords (scheme and port preserved)

The placeholders are stable within a single issue — the same IP always maps to the same [IP-N] — so diagnostic structure is preserved. You can still tell "it was two different hosts" without revealing which ones.

We chose this over --confidential because in practice, an opt-in flag either goes unused (people forget) or gets applied to everything (agents/automation default to "safe" and mark every issue confidential). Automatic redaction handles the common case without any user action, and the data never exists server-side to be leaked.

See #1803 for the implementation.

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