Cairn

Kanban respawn guard bugs and operator overrides

NousResearch/hermes-agent · cluster 29458 · agent

Data as of

10 open items. Fix attempted, not merged.

The short answer

4open issues
6open PRs
16items grouped
Known?
Yes. 16 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 5 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
4 issues and 6 PRs.

Multiple bugs and fixes related to the Kanban dispatcher's active_pr and recent_success respawn guards incorrectly blocking task dispatch, with no operator path to clear the guard. Members address guard logic for closed PRs, false triggers, and adding override/unguard mechanisms.

Open issues4

  • Issue#29458[Bug]: Kanban active_pr respawn guard has no operator clear path and ignores closed PRs
  • Issue#49870[Bug]: '→ ready' button on Done tasks triggers false diagnostic and respawn guard blocks dispatcher
  • Issue#62418Kanban dispatcher's active_pr respawn guard blocks legitimate rework after unblock, no bypass short of manual claim+spawn
  • Issue#67249active_pr respawn guard has no operator override and can be tripped by non-PR content in comments

Open PRs6

  • PR#46204fix(kanban): let PR feedback unblock respawn guard
  • PR#49871fix(kanban): '→ ready' button triggers false diagnostic and respawn guard blocks dispatch
  • PR#62424fix(kanban): allow respawn after explicit unblock
  • PR#65948fix(kanban): only guard open pull requests
  • PR#136185fix(kanban): an operator re-queue lifts active_pr, and a long hold notifies subscribers
  • PR#138302fix(respawn_guard): release merged/closed PR cards (upstream #29458)

5 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1 · partial fix 1 · superseded by another PR 1 · other 1

  • #29492 fix(kanban): check GitHub PR state before applying active_pr respawn guard · partial fix → #46204, #29492
  • #42134 feat(kanban): add 'unguard' command to clear respawn guard for a task · done elsewhere → 77db9d6, #42053
  • #68198 fix(kanban): add operator override for the active-PR respawn guard (#67249) · other
  • #104861 fix(kanban): reset stale ready-age diagnostics · duplicate → #28703, #49871, #49870
  • #111865 fix(kanban): attribute active PR guard to task · superseded by another PR → #62418, #111862, #109601
Closed issues · 1
  • Closed#42053[Bug]: Kanban `recent_success` respawn guard has no operator clear path — task permanently stuck in ready after re-comment
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.12: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
1
Attempts
5 PRs closed without merging

For your agent

The same facts, typed.

cluster/29458.json
cluster/29458.md