OpenAI Open-Sources Rust Rewrite of Codex Terminal Coding Agent with ~25x Faster CLI Startup
On August 22, OpenAI's terminal coding agent openai/codex hit GitHub Trending, gaining over 1,500 stars in a single day to reach 113,312 total stars. Unlike the earlier open-sourcing of the Codex Harness (Apache-2.0, deployment stack layer), this is a ground-up rewrite of the CLI layer: Rust replaces the previous Node implementation, compressing startup time to about 1/25 of the original. Pressing enter and having the agent ready to respond is now nearly instantaneous.
Why Rust, and Why Now
The Codex repository was first open-sourced in April 2025, but it was weighed down by long Node startup chains, TUI assembly, and model handshakes. It remained the "baseline" terminal coding agent for two years, but as Cursor, Claude Code, and Aider all got faster, Codex risked being left behind.
This rewrite delivers on OpenAI's internal CLI lifecycle engineering:
- Thread — long-lived sessions
- Turn — complete execution rounds
- Item — the minimal unit: model messages, command executions, file modifications, tool calls
- obra/superpowers — 276K stars
- affaan-m/ECC — 242K stars
- mattpocock/skills — 232K stars
- openai/codex — 113K stars
The App Server streams NDJSON events such as turn/started, item/*, and turn/completed, letting clients see every command execution, code patch, and approval flow in real time.
That's why startup feels transformative: a Codex CLI launch used to take 3+ seconds; it's now on the order of 100ms, restoring the natural rhythm of conversation.
What the 113K Stars Mean
First, GitHub Trending's top four that day were all part of the "skills economy" ecosystem:
Second, Codex CLI's security model is among the most rigorous in this stack: tool execution must pass permission checks, sandboxes are selected by policy, and it can interrupt and request human approval when needed. Codex positions itself as an "industrial-grade safe runtime," not a model-neutrality arena. This draws a clear line from Claude Code and Cursor, which aim for compatibility across vendors — Codex is deeply bound to OpenAI's own ecosystem by default.
A Notable Engineering Detail: Missing Cache Control on Bedrock
Running openai/codex on AWS Bedrock hides a billing trap (issue #37674, closed August 21): Bedrock does not allow Codex to enable explicit prompt caching for GPT-5.6 Sol, causing the agent workflow to generate large volumes of cache-write tokens at significantly higher cost than other routes. OpenAI classified it as an "enhancement" (missing feature), not a "bug" (mis-billing) — so no refunds are coming; the extra money spent comes directly from missing cache control.
For production teams, this matters: audit your bills not for Bedrock anomalies, but for the share of cache-write tokens in your usage.
What This Actually Changes
It pulls the "default venue" for AI coding assistants back to the command line. In shells, SSH sessions, CI runners, Docker containers, and remote jump hosts — traditional engineer environments where Python venvs are slow and IDEs can't be installed — making Codex work previously required hacking together aliases. Now a Rust single binary just runs. This "install-and-go" quality is an infrastructure-level win.
For OpenAI, the move positions Codex as the runtime under the Harness: skill frameworks like Superpowers sit on top, proxy gateways like Sub2API sit below, and the runtime itself does one thing only — get instructions into the filesystem and shell. This "narrow and deep" strategy is more likely to survive than trying to build a do-everything IDE.
Codex is still in alpha with a fast release cadence — pinning a version for production is the prudent choice. But regardless of who wins this war, the Rust CLI rewrite has already raised the industry's floor to 100ms startup. The next time a coding agent feels slow, nobody will go back to a Python implementation.
GitHub: https://github.com/openai/codex (113,312 stars, +1,544 on Aug 22)
References: Smartotics AI Daily Report 8/23, Dev Breakfast Daily Intel 8/23, GitHub Trending 8/23, cooconsbit analysis, AppServer protocol docs, issue #37674 (Enhancement, closed 8/21), Reddit r/LocalLLaMA discussion