Cairn
NousResearch/hermes-agent

Kanban worker exit-code mapping for rate limits

Cluster 48000 · cron. Data as of

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

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 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.

These items address a bug where single-query kanban workers bypass exit-code mapping, causing transient rate-limit or provider outage events to incorrectly trip the circuit breaker. The fixes involve reclassifying clean exits via log inspection and broadening transient-failure detection.

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

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #48005 fix(kanban): apply exit-code mapping to single-query (-q) workers and broaden transient-failure reasons · other
  • #55476 fix(kanban): reclassify rate-limited clean exits via worker log inspection (#55445) · done elsewhere → 1b2a75f, #112500, #110917, #97623
Closed issues · 1
  • Closed#48000kanban workers (`chat -q`) bypass the rate-limit/failure exit-code mapping → transient provider outage trips the circuit breaker
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.50: 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
#112500
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
16 Sep 2026

For your agent

The same facts, typed.

cluster/48000.json
cluster/48000.md