Cairn
NousResearch/hermes-agent

Kanban worker protocol-violation errors hide the real cause

Cluster 46593 · cron. Data as of

1 open item. Fix merged in #112618 on 16 Sep 2026. Check it covers your case.

The short answer

1open issue
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues 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 unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

Most members concern kanban workers that exit (rc=0) without calling kanban_complete, or crash, where the board shows a bare 'protocol violation' while the real error stays in logs. Several are duplicates, and one fix-oriented PR proposes surfacing the worker's actual output or error; one member mentions a JTAPI show-tech fix, which may be a specific instance of the same symptom.

Open issues1

  • Issue#63504Kanban dan-pr worker crashes/protocol violation block JTAPI show-tech fix

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: done elsewhere 1

  • #46985 fix(kanban): surface real worker error instead of bare "protocol violation" · done elsewhere → 2cfb655, #112618, #88815, #88603
Closed issues · 2
  • Closed#46593kanban: worker exits rc=0 without calling `kanban_complete` shows unhelpful 'protocol violation' — real error buried in logs
  • Closed#46889kanban: worker exits rc=0 without calling `kanban_complete` shows unhelpful 'protocol violation' — real error buried in logs
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.31: 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
2
Attempts
1 PR closed without merging
Fix link checked
16 Sep 2026

For your agent

The same facts, typed.

cluster/46593.json
cluster/46593.md