Rank, 14 days: 87 on the Codex sheet
5 people reported
All time, since Oct 20, including 1 thumbs-up on GitHub.
Image-heavy reconnect loop
“Each WebSocket handshake succeeded, but the client retried the full request five times before falling back to HTTP.”
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/20215/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
Image-heavy conversations reconnect repeatedly, then fall back to HTTP. Retained inline images make the replayed request very large; the WebSocket closes before response.completed, shows "Reconnecting 5/5", then HTTP resends the full context.
Is this your bug?
File my report- Where
- Responses WebSocket
- Error text
stream disconnected before completion: websocket closed by server before response.completed- Versions
- 0.166.0
- Platforms
- Linux, macOS, Windows
- How bad
- Breaks a normal workflow.
Related: Response stream disconnects mid-task
Not quite your bug?
- Old images resent each request13 people
- Image-heavy threads disconnect2 people
- Image history overflows Bedrock2 people
Original reports4, newest first
- Oversized image history closes Responses WS at 16 MiB; compact over HTTP, then resume WSOn GitHub#59703
- [Windows App] Image-heavy fork replays ~443 MB of history, repeatedly reconnects, then falls back to a ~301 MB HTTP requestOn GitHub#58847
- Oversized WebSocket replay causes persistent HTTP fallback and repeated image uploads; batched generate:false replay succeedsOn GitHub#58497
- Retained images exceed Responses WebSocket size limit: five retries before HTTP fallback; 16 MiB ± 1 byte reproductionOn GitHub#55730