Cairn
NousResearch/hermes-agent

Kanban auto-decompose blocking dispatch cycle fix

Cluster 106985 · cron. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These items address a problem where the auto-decompose tick in the Kanban dispatcher runs synchronously, blocking ready-task spawns. The proposed fixes involve running auto-decompose as a background task to prevent slow triage decomposition from starving other dispatch operations.

Open issues1

  • Issue#106985Kanban dispatcher's auto_decompose tick blocks the entire dispatch cycle synchronously

Open PRs1

  • PR#106998fix(kanban): run auto-decompose as a background task so a slow triage decompose can't starve ready-task spawns

1 PR closed without merging

From the close comments: partial fix 1

  • #106990 fix(kanban): do not block ready spawn on auto-decompose · partial fix → #106985, #106998
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/106985.json
cluster/106985.md