Improve kanban block refusal error messages

NousResearch/hermes-agent · cluster 133358 · cron

Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These items address unclear or missing information in kanban_block refusal responses, including adding reason explanations and identifying the refusing branch when a block is rejected.

Open issues1

  • Issue#133358kanban_block refusal for a stale worker says 'unknown id or not in running/ready' (block_task has no with_reason, unlike request_review)

Open PRs2

  • PR#133371fix(kanban): explain block refusal reasons
  • PR#133374fix(kanban): name the refusing branch when kanban_block refuses
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: 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
cron
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.