Skip to main content
← Back to list
01Issue
BugShippedSwamp CLI
Assigneesstack72

Relationships

#1635 extension/guide.md quick reference uses -j, which no swamp command accepts

Opened by aaronge · 8/13/2026· Shipped 8/13/2026

The swamp extension skill guide quick-reference table uses -j as shorthand for --json in two rows, but no swamp command accepts -j, so copying either row verbatim fails.

Location

  • references/extension/guide.md:106 — | Next version | swamp extension version --manifest m.yaml -j |
  • references/extension/guide.md:109 — | Check formatting | swamp extension fmt manifest.yaml --check -j |

Reproduce

$ swamp extension version --manifest manifest.yaml -j
[FTL] error: Error: 'Unknown option "-j". Did you mean option "-h"?'

$ swamp extension version --manifest manifest.yaml --json
{ "extensionName": "...", "nextVersion": "2026.08.13.1" }

Scope

Not specific to extension version. -j is rejected by every command tested: model list, extension version, workflow search, data search, auth whoami. swamp --help lists only --json as the global JSON option; the only global short forms are -h/--help, -q/--quiet and -v/--verbose.

Expected

Either the two doc rows use --json, or -j is added as an alias for --json (which would be consistent with -q and -v already having short forms).

Impact

Low severity but high copy rate: a quick-reference table is the part most likely to be used verbatim, including by agents following the skill. Hit while publishing an extension — the failure is obvious and self-correcting once you notice the error, but it is a dead end for anything copying the documented form.

Environment

swamp 20260809.004828.0-sha.b61c9de2, macOS (darwin arm64)

02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 3 MOREPR_LINKED+ 2 MORESESSION_SUMMARIZED

Shipped

8/13/2026, 3:05:59 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack728/13/2026, 2:48:55 PM
Editable. Press Enter to edit.

stack72 commented 8/13/2026, 3:06:12 PM

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

Sign in to post a ripple.