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)→

Original post →

More from coding & agent

coding & agent channel →