Agent turn stalls and compression retry fixes
Cluster 78981 · agent. Data as of
Nothing open on GitHub. Fix merged in #97695 on 29 Aug 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 #97695. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #96634. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address scenarios where agent turns become permanently stuck or 'ghost' due to stalled streams or errors in context compression, and introduce retry and recovery logic to handle such hangs. A reported case involves a DeepSeek 500k-token session where stalled stream waits hit a 600s ceiling, leaving interrupted turns and later messages unable to start a new turn.
Open issues0
Open PRs0
Fixes on record
-
#96634 fix(compression): retry a stalled summary on the fallback chain (#78981)
files:
agent/auxiliary_client.py,agent/context_compressor.py,agent/conversation_compression.py,contributors/emails/[redacted:email],contributors/emails/[redacted:email],run_agent.py,tests/agent/test_compression_stall_fallback_78981.py,website/docs/user-guide/configuration.md -
#97695 fix(agent): count only substantive auxiliary progress (#96667 salvage)
files:
agent/auxiliary_client.py,tests/agent/test_aux_progress_streaming.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#80122 fix(agent): handle auxiliary stream stalls and prevent turn ghosting · merged via another change →
#97695,#96634
Closed issues · 1
- Closed#78981Session permanently dies after repeated context-compression hangs (DeepSeek 500k-token session): stalled stream waits 600s ceiling, interrupted turn never recovers, later messages never start a turn
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