Codex hit an HTTP fallback trap: oversized turns re-uploaded on every request
charliermarsh · x · 2026-11-21
charliermarsh (Ruff author, Codex team) shares an engineering war story: an oversized turn used to be mostly uploaded over WebSocket before the server rejected it, then the client retried — all wasted time. Worse, once stuck on a large turn the client fell back to HTTP, which lacks incremental sends, so the whole "large turn" was re-uploaded on every subsequent model request.
Related event: Codex raises WebSocket limit to 128MB, cutting HTTP fallback ~20%(5 posts)→
More from coding & agent
- CapCut ships ChatGPT plugin for prompt-to-video with editable timeline via MCP — HeyZoyaKhan · 2026-11-21
- ENZO open-source self-hosted AI workspace unifies free-tier APIs and local models — anonymous20256 · 2026-11-21
- Codex raises WebSocket limit to 1 GB, big speed gains on large turns — charliermarsh · 2026-11-21
- Codex raises WebSocket request limit 8x to 128MB, making large turns 5x faster — charliermarsh · 2026-11-21
- Neon boosts Antigravity cache hit rate ~4%, raising quota effectiveness by at least 20% — cgarciae88 · 2026-11-21
- ArcFront launches with 4 of 5 frontier labs as customers, targeting agent evals — eptwts · 2026-11-21