The Wire ยท Showcase
CODEX TIGHTENS PROXY ENFORCEMENT, SDK CLIENTS SHIP GPT-5.6-SOL SUPPORT
By RepoJournal ยท Filed ยท About OpenAI
Codex closed a proxy bypass hole in file uploads while both Node and Python clients landed new model capabilities overnight.
The Codex team plugged a critical gap where file upload flows could ignore system proxy settings even after API requests honored them [1]. The fix makes HTTP client policy a required input across the three-step upload process (create record, PUT bytes, finalize), resolving each destination independently so no step can slip through the configured proxy. On the SDK front, both openai-node v6.46.0 and openai-python v2.45.0 shipped with gpt-5.6-sol model updates [3] [4], though the Python release also had to restore beta resource accessors that got inadvertently stripped [4]. In parallel, Codex is fixing its conversation tracking by properly forwarding originator headers to ChatGPT-hosted Apps and plugin-runtime MCP requests [2], resolving production validation gaps where plugin creation logs were showing `CODEX_UNKNOWN_DEFAULT` instead of actual surface origins. Internal cleanup work removed the redundant `NetworkProxyConfig` wrapper that forced runtime callers to repeat `.network` everywhere , and the TUI now strips empty reasoning-summary placeholders that were leaking into transcript history .
Action items
- โ Update openai-node to v6.46.0 and openai-python to v2.45.0 for gpt-5.6-sol model support openai/openai-node [plan]
- โ Deploy Codex file upload proxy fix [ref:1] to staging immediately if handling sensitive proxy configurations openai/codex [plan]
- โ Monitor Codex originator header forwarding [ref:2] in production logs for correct project creation attribution openai/codex [monitor]
References
- [1] codex-api: route file uploads through HTTP client factory โ openai/codex
- [2] fix: forward originator to Codex Apps MCP โ openai/codex
- [3] v6.46.0 โ openai/openai-node
- [4] v2.45.0 โ openai/openai-python