3 people reported
All time, since Oct 12.
Stream disconnected errors
“It materially interrupts ordinary work and also occurs when retrying.”
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/11931/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
Desktop tasks fail with stream disconnected before completion errors. Local tasks end with "An error occurred while processing your request" after read-only commands or searches finish; retries and follow-up messages hit the same failure.
Is this your bug?
File my report- Where
- Codex desktop app
- Error text
stream disconnected before completion: An error occurred while processing your request.- Versions
- 26.1007.30912
- Platforms
- macOS, Windows
- How bad
- Breaks a normal workflow. Some reports say it blocks them completely.
Part of: Response stream disconnects mid-task16 bugs
- Stream disconnects mid-response7 people
- Stuck on Reconnecting3 people
- Stream disconnects mid-task5 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
- 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
Original reports3, newest first
- Windows Codex app: repeated Reconnecting 5/5 and stream-disconnected errors across follow-up turnsOn GitHub#53446
- Windows desktop: repeated stream disconnections with server processing errors across a fresh taskOn GitHub#53428
- [macOS][Codex Desktop] Repeated “stream disconnected before completion” failures after successful local commandsOn GitHub#53315