$ the-wire · showcase
CODEX CONSOLIDATES HTTP PLUMBING ACROSS CORE AND CLI
By RepoJournal · Filed · About OpenAI · Composed from the cited sources · methodology
OpenAI shipped four targeted refactors across Codex in the past 24 hours, each tightening dependency ownership and routing logic to reduce technical debt.
The most consequential change removes codex-core's direct reqwest dependency [1], consolidating HTTP handling through the dedicated codex-http-client layer. That same consolidation logic now applies to pet asset downloads, which moved from a standalone blocking client to an async-capable RouteAwareClientPool [2], ensuring CDN redirects respect Codex's configured route handling. On the CLI side, cloud-managed MCP server definitions now load before list, get, login, and logout commands [3], letting enterprise users interact with managed servers while keeping add and remove operations scoped to local configuration. Documentation routing got refined too [4], making official OpenAI docs the default first search target while splitting self-knowledge and setup guidance into focused references. The cleanup also removed obsolete rusty_v8 146.4.0 Bazel targets [5], leaving only the 150.4.0 build targets in place.
Action items
- → Review dependency exceptions for any remaining HTTP client usage in codex-core openai/codex [plan]
- → Test MCP cloud server loading in your enterprise CLI workflows openai/codex [monitor]
- → Validate pet asset downloads work on your configured CDN routes openai/codex [monitor]
References
- [1] Remove codex-core's direct reqwest dependency (#36076) openai/codex ↗
- [2] Route pet asset downloads through the shared HTTP client (#36008) openai/codex ↗
- [3] Load cloud-managed servers in MCP CLI commands ↗ openai/codex
- [4] Refine OpenAI docs skill source routing ↗ openai/codex
- [5] Remove obsolete rusty_v8 146.4.0 Bazel targets (#35997) openai/codex ↗