A workflow declares its inputs in full — types, defaults, descriptions, and which are required — but none of it appears in either JSON reader. The declaration is recoverable only by reading the workflow YAML at path, which is not possible for a client talking to a remote orchestrator over the socket.

A workflow declares inputs properly

inputs:
  properties:
    labelKey:
      type: string
      default: role
      description: Label key to select on.
    labelValue:
      type: string
      default: ""
      description: Label value; omit to target everything.
    refresh:
      type: boolean
      default: true
      description: Refresh metadata first.
  required: []

Neither JSON reader returns any of it

swamp workflow get <workflow> --json
# → {id, name, description, version, jobs[], path}   — no inputs (also no tags, no reports)

swamp workflow search --json
# → results[] = {id, name, description, jobCount}     — no inputs, no hasInputs

workflow schema get is the schema for workflow files, not for a given workflow's inputs, so there is no third place to look.

Impact

Any tool that wants to present or prompt for a workflow's inputs — a UI, a wrapper CLI, a scheduler — can describe a workflow only as a name, a description, and a job count. Without the input schema it must either:

launch every workflow on its declared defaults with no way to override them — and for an input like labelValue: "" meaning "everything", that silently selects the broadest possible target; or
invent form fields it cannot validate against the real declaration.

Parsing the YAML at path is not a workaround for a remote caller: the file is on the orchestrator host, not the client's.

Ask

Include inputs (the full properties map with types, defaults, descriptions, and required) in swamp workflow get --json.
Optionally, add a required/hasInputs hint to swamp workflow search --json so a list view can flag which workflows take parameters without an N+1 round-trip.

Bonus: workflow get --json also omits tags and reports, which are likewise declared in the file but unreadable over the socket — including them in the same pass would close the broader "the JSON reader is lossy versus the file" gap.

02Bog Flow

Shipped

7/26/2026, 11:21:02 PM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack727/26/2026, 10:48:22 PM

stack72 commented 7/26/2026, 11:21:10 PM

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

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

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

Documentation for workflow assert steps and JUnit output

Expose workflow inputs in WorkflowReportContext

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

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

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

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

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)

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

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

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

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

Hide enterprise (SSO) operatives from announcements and leaderboard by default

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

Published extension scores dependency-trust as "missing" (0/2) while client `extension quality` earns it (2/2); no verdict exposed

Add a :micdrop: emoji / reaction shortcode (swamp-native art included)

namespace unset --migrate silently deletes artifact history via catalog-rebuild GC (~484k files lost)

serve: workflow.approvals and workflow.run.search still full-scan the workflow-run store after the #1284 data.query pushdown

Bugs filed by a team-subscription user are not tagged "team" in the Lab

Bundled extension model cannot deserialize AWS SDK S3 XML that works in direct Deno

gcp/sheets spreadsheets-values: batch_get crashes with "Request with GET/HEAD method cannot have body"