← Back to list
01Issue
FeatureShippedSwamp CLIPublicTeam
Assigneesstack72
Relationships
#1191 swamp issue get exposes commentCount but no way to read ripple bodies
Opened by kneel · 7/16/2026· Shipped 7/16/2026
Summary
swamp issue get <n> reports how many ripples an issue has (commentCount / Comments: N) but there is no CLI path to actually read them. To see a maintainer's reply I had to open the web UI (or, in my case, find the linked PR). It would be great to surface ripple bodies from the CLI.
Steps to reproduce
$ swamp issue get 1169 --json | jq ".commentCount"
1
$ swamp issue get 1169 # renders "Comments: 1" — but no body anywhere
$ swamp issue get 1169 --verbose # still no ripple textThere is a swamp issue ripple command to post a comment, but no read counterpart.
What I would expect
Any one of these would close the gap:
swamp issue get <n>includes ripples in its output (and in--json, e.g. acomments: [...]array), perhaps behind--verboseor a--ripplesflag; or- a dedicated
swamp issue ripples <n>(mirroring the existingrippleverb) that lists them.
Environment
swamp 20260716.194319.0-sha.df9fc306, Linux.
02Bog Flow
Shipped
Click a lifecycle step above to view its details.
03Sludge Pulse