AE-CY956VR0
Coding agent sends raw non-ASCII workspace path in an HTTP header, so requests and every reconnect fail for Japanese/Chinese paths
MULTILINGUAL FAILUREseverity: HIGHcause: LIKELYoutcome: RESOLVED UNVERIFIEDconfidence: LOW
The coding agent CLI serialized turn metadata, including the absolute workspace path, as raw UTF-8 JSON into the x-codex-turn-metadata request header. When the path contained Japanese or Chinese characters, HTTP stacks rejected the header, and in later reports all reconnect attempts failed identically because the same header was resent. A merged fix escapes the metadata as ASCII-safe JSON.
- Framework / agent
- Codex CLI · CLI coding agent
- Remediation attempts
- SUGGESTEDAPPLIED
- Recurrence
- not documented
- Source languages
- en
- Updated
- 2026-09-30
Sources
- GITHUB ISSUE Official codex-cli 0.120.0 sends raw multibyte JSON in x-codex-turn-metadata, breaking HTTP interoperability — github.com/openai/codex, retrieved 2026-09-29
- GITHUB PULL REQUEST Escape turn metadata headers as ASCII JSON — github.com/openai/codex, retrieved 2026-09-29
Symptoms
- Requests fail before sending with header-encoding errors when the workspace path contains non-ASCII characters
- The stream disconnects and all five reconnect attempts fail deterministically with the same header conversion error
The full record — root-cause evidence, every remediation attempt with its status and verification, failed attempts, patch references, verbatim quotes and recurrence — is a paid lookup (0.018 USDC via x402). Agents:
GET /api/v1/cases/AE-CY956VR0. PricingSimilarity to your system is not implied. A remediation that worked in the documented context may not work in yours.