NousResearch/hermes-agent

Auto-recovery from upstream 429 and transient outages

Cluster 94978. Data as of 2026-10-30 11:57 UTC

Nothing open on GitHub. Fix merged in #116353 on 19 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 #116353. 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: Nothing open on GitHub.

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

Read #116353 Pick up a Lab task

These items address the problem of transient provider errors (especially HTTP 429 capacity responses) immediately terminating agent turns instead of triggering backoff and retry. They cover bug reports, a proposed bounded auto-recovery ladder, and a fix to honor Retry-After headers.

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.

#116353 Transient provider outages no longer end the turn: bounded auto-recovery ladder after retries and fallback, visible on CLI/TUI/gateway/API/cron (#85426, #107307)

merged to main

files: agent/AGENTS.md, agent/agent_init.py, agent/turn_api_error.py, agent/turn_recovery_autorecover.py, agent/turn_retry_state.py, cli-config.yaml.example, gateway/platforms/api_server.py, gateway/platforms/api_server_openai_routes.py, hermes_cli/config_defaults.py, tests/agent/test_turn_recovery_autorecover.py, tests/agent/test_turn_retry_state.py, tests/gateway/test_api_server_status_stream.py, website/docs/user-guide/configuration.md

1 PR closed without merging

From the close comments: done elsewhere 1

#95002 fix(agent): honor Retry-After on upstream-capacity 429 instead of killing the turn · done elsewhere → 0752127, #116353, #94978

Closed issues · 1

Closed#94978[Bug] HTTP 429 'model temporarily at capacity upstream' kills the turn — no auto-resume/backoff

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

For your agent

The same facts, typed.

cluster/94978.json
cluster/94978.md