NousResearch/hermes-agent

Kanban dispatcher unknown-assignee handling and diagnostics

Cluster 122422. Data as of

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

The short answer

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

These items address a bug where the Kanban dispatcher silently drops cards with an unknown assignee, leaving them stuck in 'ready' with no feedback. Fixes add per-task event logging for skipped assignments and resolve related worker boot and credential exit issues.

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.

  • #126153 Kanban workers boot on store-Python installs; unknown assignee, gh identity and dead-credential exits fixed (#122299 #122487 #122500 #122422 #122689, salvage #122420 #122567 #122714 #122716)

    merged to main

    files: cron/scheduler_delivery.py, hermes_cli/auth_codex.py, hermes_cli/cli_agent_setup_mixin.py, hermes_cli/cli_single_query.py, hermes_cli/kanban_db_dispatch.py, hermes_cli/kanban_pr_acceptance.py, hermes_cli/kanban_pr_acceptance_store.py, tests/hermes_cli/test_kanban_credential_startup_exit.py, tests/hermes_cli/test_kanban_db.py, tests/hermes_cli/test_kanban_dispatch_unknown_assignee_event.py, tests/hermes_cli/test_kanban_pr_acceptance.py, website/docs/user-guide/features/kanban.md

1 PR closed without merging

From the close comments: other 1

  • #122567 fix(kanban): write per-task event when dispatcher skips unknown assignee · other → #122422, #126153, #122567
Closed issues · 1
  • Closed#122422Kanban dispatcher silently drops cards with an unknown assignee — card sits in `ready` forever with zero board diagnostics
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
#126153
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
28 Sep 2026

For your agent

The same facts, typed.