2 people reported
All time, since Oct 9.
Image-heavy threads disconnect
“Desktop document-preview images accumulate again after recovery; individual threads repeatedly reconnect and remote compaction can fail”
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/9348/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
Threads with accumulated images fail with stream disconnected errors. After image generation or reading rendered document pages as images, affected threads keep reconnecting and turns or /compact fail.
Is this your bug?
File my report- Where
- Codex desktop app
- Error text
stream disconnected before completion: websocket closed by server before response.completed- Versions
- 0.162.0-alpha.2
- Platforms
- macOS
- 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
- 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
- Stream disconnects mid-response2 people
Show all 15Show only the largest 10
- Stuck reconnecting to network2 people
- Context compaction fails4 people
- Endless reconnect loop4 people
- Remote compaction idle timeout5 people
- Workspace routing timeouts4 people
Not quite your bug?
- Old images resent each request13 people
- Image-heavy reconnect loop5 people