Nothing open on GitHub. Fix merged in #115900 on 19 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #115900. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #115900. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where superseded Codex streams continue consuming data, causing truncated output in Telegram replies even when display streaming is disabled. The fixes aim to ensure superseded streams are still fully consumed so final text is not cut off.
Open issues0
Open PRs0
Fixes on record
-
#115900 fix(codex): superseded streams keep consuming so final text is not truncated (#69486, salvage #69502)
files:
agent/codex_runtime.py,contributors/emails/[redacted:email],tests/agent/test_codex_request_transport_diagnostics.py,tests/agent/test_codex_stream_supersession.py,tests/agent/test_run_agent_codex_responses.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#69502 fix(codex): keep consuming superseded streams · merged via another change →
b1e7460,#115900,#69486,#69502
Closed issues · 1
- Closed#69486Telegram reply can truncate after Codex stream supersession even with display streaming disabled
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.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 LabAt a glance
- Subsystem
- agent
- Merged PRs
- #115900
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 Sep 2026