# NousResearch/hermes-agent · Kanban run row stuck in running state fixes

## Open now

- Nothing open on GitHub.

These items address cases where kanban run rows remain in a 'running' state incorrectly, including dead workers being inconsistently handled, rows missing worker PIDs, and rows not transitioning after a worker exits cleanly.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #114904. Verify it addresses your case.
- **Recommended:** read PR #114904 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-114904`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #113610: \[Bug\]: kanban run row stays 'running' after a worker exits rc=0 with no terminal transition — classification is inconsistent across runs

## Prior & competing PRs

- **#114904: fix(kanban): a dead worker is booked the same way whichever dispatcher process notices it, and a tripped violation budget holds the card (#113611, #113610, salvage #113638)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `cli.py`, `hermes_cli/kanban_db.py`, `hermes_cli/kanban_db_dispatch.py`, `hermes_cli/quiet_single_query.py`, `tests/hermes_cli/test_kanban_worker_exit_trailer.py`, `website/docs/user-guide/features/kanban.md`
- **#113632: fix(kanban): reclaim running rows that never recorded a worker PID**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#114904`, `#113632`

## Fix status

- Merged to main in PR #114904 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-18`.