NousResearch/hermes-agent

Kanban worker silent failure on protocol violation

Cluster 88603 · cron. Data as of 2026-10-29 11:48 UTC

Nothing open on GitHub. Fix merged in #112618 on 16 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 #112618. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #112618. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #112618 Pick up a Lab task

These items concern a scenario where a Kanban worker violates its protocol and is silently respawned in a loop, with no mechanism to surface or display the worker's own final output when the violation or crash occurs. The work focuses on exposing that last output to aid diagnosis.

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.

#112618 Kanban board shows the worker's own last output on protocol violations and crashes (#88603, #46593, salvage #88815)

merged to main

files: hermes_cli/kanban_db_dispatch.py, tests/hermes_cli/test_kanban_core_functionality.py, website/docs/user-guide/features/kanban.md

1 PR closed without merging

From the close comments: merged via another change 1

#88815 fix(kanban): surface worker's own final text on protocol_violation · merged via another change → 2cfb655, #112618

Closed issues · 1

Closed#88603[Bug]: A Kanban worker that cannot satisfy its protocol has no way to say so — silent protocol_violation and a respawn loop instead

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
Merged PRs: #112618
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 16 Sep 2026

For your agent

The same facts, typed.

cluster/88603.json
cluster/88603.md