5 people reported
All time, since Sep 14, including 4 thumbs-up on GitHub.
Remote compaction idle timeout
“Remote context compaction in Codex App / Work repeatedly fails when the context window reaches approximately 84–86%.”
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/16893/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
Remote context compaction fails with idle timeout waiting for SSE. Fails when the context window reaches about 84-86% in Work threads, after a "Reconnecting 2/2" message, even with a working Responses WebSocket.
Is this your bug?
File my report- Where
- Codex App Work
- Error text
stream disconnected before completion: idle timeout waiting for SSE- Versions
- 0.154.0
- 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
- Context compaction fails4 people
- Endless reconnect loop4 people
- Workspace routing timeouts4 people
Not quite your bug?
- Remote compaction stream failure6 people
Original reports1, newest first
- [Windows][Codex App][Work] Remote context compaction fails at ~84% with "idle timeout waiting for SSE" even when Responses WebSocket is healthyOn GitHub#45472