Fix: Codex CLI zstd Compression 400 Error A developer reported that Codex CLI 0.167.0 returns a bare 400 Bad Request from chatgpt.com/backend-api/codex/responses when zstd-compressed request bodies contain a part that decompresses far beyond its compressed size, while the same request sent uncompressed succeeds. The issue (openai/codex#61489) remains open with no staff reply as of Nov 15, 2026, and related reports #60594 and #41338 show the same pattern. No verified user-side fix exists: compaction carries the same payload, and disabling request compression is discussed but unverified. Originally published on DebugRadar https://debugradar.com/fix-codex-cli-zstd-compression-400-error/ . 400 {"detail":"Bad Request"} on chatgpt.com/backend-api/codex/responses when the zstd-compressed body contains a part that decompresses far beyond its compressed size. The same request uncompressed succeeds. | Error Code | Affected Version | Root Cause | Current Status | |---|---|---|---| | Bare 400 {"detail":"Bad Request"} on requests to chatgpt.com/backend-api/codex/responses | Codex CLI 0.167.0, ChatGPT auth Pro 500 , gpt-6.1-sol, Linux x86 64 CentOS 8 | The backend rejects highly compressible zstd bodies features.enable request compression , default on for ChatGPT auth . The documented rule is a 413 at 100x expansion — the backend returns a bare 400 instead, and Codex never retries uncompressed. Per-block expansion triggers it: a 2.65x overall ratio still failed in the related 60594 report. | Still open as of Nov 15, 2026 — openai/codex 61489, 12 comments, last activity Nov 15 03:30 UTC, no staff reply. Weakest of this batch on the workaround axis: no verified fix, CLI-only, Linux-heavy, very technical | Confirm the three-way pattern before you change anything: the request fails with a bare 400 while zstd compression is on, and the same request succeeds uncompressed. If the uncompressed request also fails, it is a different problem — do not chase the compression angle. Compaction will not help — it carries the same payload, so the compressed body trips the same backend limit. Do not waste a session compacting to work around this. Shrinking the request is the only mitigation on the table, and it is untested — flag it honestly. A smaller, less repetitive body is less likely to trip the per-block expansion limit, but nobody has verified that shrinking fixes a failing request. Try it on a copy, not on your live session. Disabling request compression is discussed in the thread but NOT verified. Do not present it as a fix, and do not change a default you cannot test back. If you try it, treat it as an experiment and report the result on the issue — the thread needs a verified workaround. This is not a one-off: 60594 HTTP 400 for repeated image inputs with zstd, Windows, Nov 10 and 41338 Aug 28, same bare 400 on a 34.78 MB body show the same pattern. The newest check Nakagawa-master, Nov 15 03:30 UTC verified the compression fallback in the current main source — distinct from the reported backend ratio limit — and there is still no staff reply. The same discipline applied to the desktop app failure in Fix: Codex Desktop App Error 0x80073D02 & 0x800706D9 https://debugradar.com/fix-codex-appx-0x80073d02-error/ — when there is no verified user-side fix, say so plainly instead of publishing a fake one. And the same family showed up in the Work Mode outage in Fix: ChatGPT Work Mode HTTP 500 Error https://debugradar.com/fix-chatgpt-work-mode-http-500/ — a bare server-side error with no user-side fix, where the honest move is evidence and a workaround. Is there a verified fix for the Codex CLI 400 error? No. There is no verified user-side fix. Disabling request compression is discussed but not verified, compaction does not help same payload , and shrinking the request is an untested mitigation. The issue is still open with no staff reply. Why a bare 400 instead of a 413? The documented rule is a 413 at 100x expansion, but the backend returns a bare 400 {"detail":"Bad Request"} instead — and Codex never retries uncompressed. The bare 400 is what makes this hard to diagnose: it looks like a bad request, but the request is fine uncompressed. Does compaction help? No. Compaction carries the same payload, so the compressed body trips the same backend limit. Do not waste a session compacting to work around this. Sources: GitHub issue, "Codex CLI zstd Compression 400 Error" openai/codex 61489 , November 14, 2026 https://github.com/openai/codex/issues/61489 https://github.com/openai/codex/issues/61489 .