Handle provider errors without losing context or work
Cluster 107307. Data as of
Nothing open on GitHub. Fix merged in #116353 on 19 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 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
resolved, deciding PR #116353. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address how transient provider outages, overload errors, and summary failures are handled, aiming to preserve conversation context and avoid interrupting ongoing agent work. The themes span retry/fallback behavior, transcript safety during compression, and user-visible error handling across interfaces.
Open issues0
Open PRs0
Fixes on record
-
#115906 fix(compression): overloaded summary provider no longer wipes the transcript with a fallback summary (#107307, salvage #107325)
files:
agent/context_compressor.py,agent/conversation_compression.py,tests/agent/test_context_compressor.py,website/docs/developer-guide/context-compression-and-caching.md -
#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)
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: merged via another change 1
-
#107325 fix(agent): preserve context when summary provider overloads · merged via another change →
4c4b0b7,#115906,#107307,#107325
Closed issues · 1
- Closed#107307[Help needed] Codex provider errors on Pro Full and Pro Light interrupt Hermes work
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.00means 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