NousResearch/hermes-agent

Kanban quota-wall exit code misclassification bug

Cluster 101800. Data as of 2026-10-25 11:21 UTC

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

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

Read #112500 Pick up a Lab task

These items concern a defect where rate-limit or quota exhaustion causes Kanban workers to exit with the wrong code (75 or clean-exit) rather than the correct sentinel, because the quota-wall condition is misidentified as a protocol violation. The work involves diagnosing the misclassification and fixing exit-code inference when failure reason metadata is absent.

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.

#112500 Kanban workers on a rate-limit/billing wall exit 75 instead of rc=0 protocol violations (#101800, #48000, salvage #110917)

merged to main

files: cli.py, contributors/emails/[email protected], hermes_cli/cli_chat_turn_mixin.py, tests/hermes_cli/test_single_query_exit_contract.py, website/docs/user-guide/features/kanban.md

1 PR closed without merging

From the close comments: done elsewhere 1

#102318 fix(cli): infer quota wall for kanban exit code when failure_reason is missing (fixes #101800) · done elsewhere → 1b2a75f, #112500, #110917, #97623, #82154

Closed issues · 1

Closed#101800Rate-limit exit sentinel is unreachable: quota exhaustion is misclassified as a clean-exit protocol violation and crashloops the board

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

For your agent

The same facts, typed.

cluster/101800.json
cluster/101800.md