swamp workflow run is currently shell-attached: the CLI process owns the run, and the run only exists for as long as that terminal stays alive. That becomes a real ergonomic problem the longer a workflow takes:

Terminal death loses your view, not your work. A laptop sleep, an SSH drop, or an accidental Ctrl-C kills the CLI process — but the docker containers it kicked off keep running, lockfiles stay held, and there's no supported way back in to either watch them finish or kill them cleanly.
No second-pane visibility. Long parallel workflows (e.g. fan-out reviewer or evaluator jobs) leave you sitting on one terminal for many minutes, unable to check progress from anywhere else. If you started the run on a remote machine, peeking from a laptop means another ssh and tail -f against a log pipe you happened to capture.
No clean cancel. If a workflow misfires, the only abort path is docker kill on the running step's container — which leaves swamp's lockfile and any partial datastore writes in an inconsistent state. There is no swamp workflow cancel that knows how to tear down cooperatively and release the lock.
Multi-user setups are blind to each other. On a shared swamp repo (a team's monorepo, a CI worker), collaborators can't see what runs are in flight, who started them, or what they're waiting on.
Failed runs leave orphaned state. When something crashes mid-run, there's no canonical record of "this run existed, here's its DAG position when it died" — reconstruction relies on whatever local log pipe got captured.

The friction compounds for any workflow that takes more than a couple of minutes. Workflows with parallel jobs (reviewers, evaluators, batch processors) sit in that window almost by definition.

Proposed shape

A small surface of commands that operate against runs as named, addressable objects:

Command	Purpose
`swamp workflow status <run-id>`	Show DAG state, current step, started/finished timestamps
`swamp workflow logs <run-id>`	Tail the run log (streaming or one-shot)
`swamp workflow cancel <run-id>`	Cooperatively cancel the run; release locks; mark cancelled
`swamp workflow list`	Recent runs across all workflows in this swamp repo

swamp workflow run would need to emit a run id on submit so it's addressable from then on (or accept --detach to fire-and-forget).

The architecture — where run state is persisted, how step processes are parented, how cancellation is signalled into docker steps, how stale-lock reaping works — is for swamp to decide. These are sketched commands, not an implementation proposal.

Affected components

swamp workflow run (run id emission, detach flag)
Workflow execution service (per-run state persistence, cancellation signal propagation)
Lockfile / datastore lifecycle (stale-run reaping, cooperative release)
CLI (new status, logs, cancel, list subcommands)

02Bog Flow

Closed

7/10/2026, 11:51:19 PM

No activity in this phase yet.

03Sludge Pulse

stack72 commented 7/10/2026, 11:51:19 PM

All four commands proposed in this issue are now implemented:

Proposed	Implemented as
`workflow status <run-id>`	`swamp workflow history get <workflow>` — shows DAG state, step status, timestamps
`workflow logs <run-id>`	`swamp workflow history logs <run-id>` — one-shot log viewing with `--tail N`
`workflow cancel <run-id>`	`swamp workflow cancel <workflow> [--run <id>] [--all] [--reason ...]` — cooperative cancel with lock release
`workflow list`	`swamp workflow history search` — recent runs across workflows

Beyond the original ask, we also shipped workflow approve, workflow reject, workflow resume, and workflow approvals for manual approval gates.

swamp serve makes all of these work remotely — workflow history logs, workflow cancel, etc. all accept --server to operate through a running serve instance without a local repo.

The one remaining gap — --follow / -f for live-tailing logs of an in-progress run — is tracked in #1081.

.swamp.yaml rewritten with quote style change + lastSkillMigrationWarning on read-only operations

Docs: document guard field for workflow steps

Add guard field to workflow steps for idempotent execution

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

tailscale transport hangs indefinitely on Tailscale SSH check-mode auth; never surfaces the login URL

Concurrent @type auto-creation races: N simultaneous runs create N definitions sharing one name, and only one is reachable

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

Extension docs still ship the Driver extension type, which the binary refuses (rejectRemovedDriverFields) after #535

Docs: document vault selection for sensitive fields (defaultVault, per-resource vaultName)

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

writeResource commits per-call: a method that fails midway leaves its earlier outputs persisted, with no marker that the run failed

Docs: document workflow-scope ReportContext fields in extension report reference

Cloudflare: expose GraphQL Analytics API (httpRequestsAdaptiveGroups / client-IP request analytics)

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

No way to select which vault receives a sensitive-marked field's value

aws-sm: namespace annotation labels with swamp:label: prefix

workflow assert: a step whose CEL expression fails to evaluate is omitted from --junit output, so the XML reports a clean pass

Documentation for workflow assert steps and JUnit output

Expose workflow inputs in WorkflowReportContext

Teach swamp skill how to write assert workflow steps

Include a workflow's declared `inputs` in `workflow get --json` (and a `hasInputs` hint in `workflow search --json`)

Docs: add how-to guide for running swamp serve/worker in daemon mode

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

swamp doctor extensions: nondeterministic BundleBuildFailed for local extensions on an unchanged tree

Docs: document datastore directory relocation during setup

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

Expose resource attributes in DataHandle for workflow report stepExecutions

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