← Back to list
01Issue
BugShippedSwamp CLIPublicEnterprise
Assigneesstack72
Relationships
#1074 --skip-reports (and --report/--skip-report*) hard-fails with --server
Opened by jeremy · 7/10/2026· Shipped 7/10/2026
Summary
model method run and workflow run both hard-fail immediately when --skip-reports (or --skip-report, --skip-report-label, --report, --report-label) is combined with --server, because the serve wire protocol has no field to carry these options. This isn't a validation bug — it's a real protocol gap: the server-side execution path has no way to honor these options even if it wanted to.
Root cause
src/cli/commands/model_method_run.ts:532-548(runMethodViaServer): builds anunsupportedlist checkingoptions.skipReports/skipReport/skipReportLabel/report/reportLabel, and throws aUserErrorif any are set:"${flags} not supported with --server yet — the serve protocol does not carry ${them}".src/cli/commands/workflow_run.ts:507-521: identical pattern forworkflow run --server.
Repro
$ swamp model method run facts list_facts --limit 3 --json --skip-reports --server ws://[REDACTED-USER]:***@[HOST-1]/method-summary"].json.outputSpecs`) regardless of which method ran. Measured on a small `coverage_gaps` call: 30,185 bytes total with reports, 12,069 of which was the schema dump alone, vs. 1,721 bytes with `--skip-reports` — the same `dataArtifacts` payload, nothing else changed.
This became a real, non-hypothetical problem for us: we updated AI agent instructions (a swamp extension's bundled skills) to always append `--skip-reports` to reduce token overhead in every method call. That works fine against a local repo, but breaks with a hard error the moment the same agent is pointed at a `swamp serve` instance instead — which is exactly the scenario `swamp serve` exists to support (remote/shared execution).
## Suggested fix
Add a field to the serve wire protocol (WebSocket/HTTP) carrying `skipReports`/`skipReport`/`skipReportLabel`/`report`/`reportLabel`, and thread it through to the server-side execution path the same way these options already work for local runs. Given how much smaller the response gets, this seems worth prioritizing rather than deferring — it's not just ergonomic, it materially affects token/bandwidth cost for any AI agent calling through serve.
## Environment
swamp 20260710.195350.0-sha.328cb36a (server), CLI client same version.02Bog Flow
Shipped
Click a lifecycle step above to view its details.
03Sludge Pulse