NousResearch/hermes-agent

Kanban cards wrongly blocked by host spawn failures

Cluster 114720. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #114886 on 18 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #114886. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #114886. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #114886, then check it covers your case.

Read #114886 Pick up a Lab task

Host-level spawn refusals (such as unreachable user D-Bus) were incorrectly consuming a card's retry budget and parking it as blocked. These members address detecting and isolating that infrastructure failure so it does not count against the card.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#114886 fix(kanban): host spawn refusals no longer park cards as blocked; oneshot-unit dispatch workers survive unit exit (#114720, #113612, salvage #113624)

merged to main

files: hermes_cli/kanban_db_dispatch.py, tests/hermes_cli/test_kanban_db.py, tests/hermes_cli/test_kanban_gateway_restart_handoff.py, tools/process_registry.py, website/docs/user-guide/features/cron.md, website/docs/user-guide/features/kanban.md

1 PR closed without merging

From the close comments: done elsewhere 1

#114760 fix(kanban): keep a host-level spawn refusal out of the card's retry budget · done elsewhere → eb28bc1, #114760, #114720

Closed issues · 1

Closed#114720[Bug]: Kanban spawn-time infrastructure failure (unreachable user D-Bus) burns the card's retry budget and parks it as a bare blocked

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

Merged PRs: #114886
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 18 Sep 2026

For your agent

The same facts, typed.

cluster/114720.json
cluster/114720.md