4 people reported
All time, since Oct 8, including 3 thumbs-up on GitHub.
Context compaction fails
“Normal conversations and model responses work correctly, but both manual and automatic context compaction fail across all tested models.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/10163/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Context compaction fails with stream closed before response.completed. Manual and automatic compaction fail in long and new conversations while normal responses work; retrying does not help, and another error reports "response protection is unavailable".
Is this your bug?
File my report- Where
- Context compaction
- Error text
stream disconnected before completion: stream closed before response.completed- Versions
- 26.1007.11041
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Part of: Response stream disconnects mid-task16 bugs
- Stream disconnects mid-response7 people
- Stuck on Reconnecting3 people
- Stream disconnects mid-task5 people
- Stream disconnected errors3 people
- Image-heavy threads disconnect2 people
- WebSocket disconnect stalls chats2 people
- Work stuck at Reconnecting 5/52 people
- Remote compaction fails2 people
- Stuck on Reconnecting 5/52 people
- Stream disconnects mid-task2 people
Show all 15Show only the largest 10
- Stream disconnects mid-response2 people
- Stuck reconnecting to network2 people
- Endless reconnect loop4 people
- Remote compaction idle timeout5 people
- Workspace routing timeouts4 people
Not quite your bug?
- Remote compaction stream failure6 people
Original reports1, newest first
- Windows Codex Desktop: Context compaction always fails with "stream closed before response.completed"On GitHub#52016