← Back to list
01Issue
FeatureClosedSwamp CLIPublic
AssigneesNone
Relationships
#4618 serve: accept a link's return code on redeem and forward it to swamp-club
Opened by skunk-ape · 11/10/2026
Closed: not doing, together with #4617, which defined the return code. Seth decided it isn't worth the cost.
Part of #4459. Sibling of #4617, which defines the return code. Read that issue for the reasoning.
Problem
swamp-club will show a one-time code at link approval and require it to complete the link. Serve's redeem route doesn't take a code, so an app can't pass it.
Proposed change
POSTredeem on serve's delegation routes accepts the code and forwards it to swamp-club.- swamp-club's refusals (a wrong code, too many attempts, no code given) reach the app as their own reasons, not as a generic failure.
- A capability, in what serve advertises, tells an app whether to ask for a code.
- swamp-lib's link calls take the code.
- Update
design/enablers/access-control.mdand swamp-uat's strict schemas.
Done when
- An app that passes the right code gets tokens, and a wrong or missing code is refused with a distinct reason.
- An app can tell from serve's capabilities whether a code is needed.
- No code reaches logs, audit,
--jsonor run records.
02Bog Flow
Closed
No activity in this phase yet.
03Sludge Pulse