Repository navigation
feat(cards): let the human unblock a card, with a guarded re-block - #112
Merged
Merged
Conversation
A ready card with an open blocker never reaches next, so a human who sees another route could not hand it back to the agent: the UI had no way to remove a blocker and `card edit --blocked-by` changed it silently. - removeBlocker + `card unblock <id> <blocker> --reason` + POST /api/cards/:id/unblock (pokes the runner like move/comment), and an x on each open blocker chip in the card view that asks for a reason. - New event kind blocker_removed; blocker changes via `card edit` now write blocker_added/blocker_removed too, never silently. - Guard: an agent re-adding a blocker the human removed must pass --reason, and core moves the card to needs_input in the same transaction, so the human decides instead of the card silently dropping out of next again. - AGENT.md rule 15: try the human's route first after a blocker_removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 15, 2026
# [0.23.0](v0.22.2...v0.23.0) (2026-10-15) ### Features * **cards:** let the human unblock a card, with a guarded re-block ([#112](#112)) ([bd0a953](bd0a953)), closes [#token](https://github.com/Robbertvermeulen/agentboard/issues/token)
|
🎉 This PR is included in version 0.23.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A ready card with an open blocker never reaches
next. When the human sees another route (e.g. task_5ae3: point 1 via a mu-plugin instead of a theme PR, which made the GH-token blocker ops_11b1 irrelevant), there was no way to hand the card back: the UI could not remove a blocker, andcard edit --blocked-bychanged it without any timeline trace.What changed
removeBlocker()in core,agentboard card unblock <id> <blocker> --reason ...,POST /api/cards/:id/unblock(pokes the runner like move/comment), and an × next to each open blocker chip on the card page that asks for a reason (suggestions: "Different route, see my comment", "No longer needed"). The blocker card itself is untouched; it may still matter for other work.blocker_removed(the existing event-table migration rebuilds the CHECK oninit).card edit --blocked-bynow writesblocker_added/blocker_removedfor every change, with an optional--reason. The timeline renders both with their reason.--reason, and core moves the card from ready/doing toneeds_inputin the same transaction (stamped with the session id). So the agent can disagree, but the card lands with the human instead of silently dropping out ofnextagain.blocker_removed, read the comments after it and try that route first; re-block only with a new reason.askReasongained optionalsuggestionsandokLabel; existing callers are unchanged.Testing
npm run buildpasses. Against an isolated data dir:mainbuild, theninitwith this build → "event table rebuilt (event kinds brought up to date)".gate; aftercard unblock ... --as humanit is ingate.card edit --blocked-by <same> --as agentwithout--reason→ refused with an explanatory error; with--reason→blocker_added+ready → needs_inputevents, card in needs_input.serve, Playwright): × on the chip opens the reason dialog, suggestion fills it, Unblock removes the chip and the timeline showsblocker_removed by human ... (Different route, see my comment).🤖 Generated with Claude Code