On August 22, OpenAI pushed its terminal coding agent openai/codex to the top of GitHub Trending, gaining 1,500+ stars in a single day and reaching 113,312 total stars. Unlike the earlier open-sourcing of the Codex harness/deployment stack (Apache-2.0), this was a complete rewrite of the CLI layer: Rust replaced the previous Node.js implementation, and startup time was compressed to roughly 1/25 of the original. Pressing Enter and having the agent ready to listen is now nearly instantaneous.
Why Rust, and Why Now
The Codex repository was first open-sourced in April 2025, but its long Node startup chain—TUI assembly plus model handshake—made it heavyweight. For two years it remained the "default" terminal coding agent, but Cursor, Claude Code, and Aider were all getting faster; standing still meant falling behind. This rewrite is the concrete deliverable of OpenAI's internal CLI lifecycle engineering: the trio of Thread (long-lived session), Turn (a full execution round), and Item (smallest unit: model messages, command executions, file modifications, tool calls) was rebuilt in Rust. The App Server streams NDJSON events—turn/started, item/*, turn/completed—so clients see every command execution, code patch, and approval step in real time.
That's why startup is fast enough to make people reconsider the tool: opening Codex CLI used to routinely take three-plus seconds; now it's on the order of 100ms, and conversational rhythm is restored.
What 113K Stars Means
Layer one: the GitHub Trending top four that day were all from the "skills economy" ecosystem: obra/superpowers (276K), affaan-m/ECC (242K), mattpocock/skills (232K), and openai/codex (113K). Codex is the execution foundation of this stack—skill frameworks ultimately need an agent that can run commands, modify files, and roll back diffs, and Codex does that with minimal overhead.
Layer two: Codex CLI's security model is among the strictest in this stack: tool execution must pass permission checks, sandboxes are selected by policy level, and execution can be interrupted for human approval when needed. Codex positions itself as an "industrial-grade secure runtime," not a model-neutrality playground. This sets it apart from Claude Code and Cursor, which aim to support many models—Codex is deeply bound to OpenAI's own ecosystem by default.
A Hidden Billing Trap: Missing Cache Control on Bedrock
Running openai/codex on AWS Bedrock has a hidden cost issue (issue #37674, closed August 21): Bedrock does not allow Codex to enable explicit prompt caching for GPT-5.6 Sol, so agent workflows generate large volumes of cache-write tokens, costing significantly more than other routes. OpenAI labeled it an enhancement (missing feature), not a bug (miscalculation)—so no refund is coming; the extra spend comes from the missing cache control. For production teams, the key check is not whether your Bedrock bill looks anomalous, but what share of your usage is cache-write tokens.
What This Actually Changes
It pulls AI coding assistants' "default venue" back from browser/desktop IDEs to the command line. In classic engineering environments—shell, SSH, CI runners, Docker containers, remote jump hosts—where Python venvs are slow and IDEs won't install, people previously needed piles of alias hacks to make Codex work; now a single Rust binary runs anywhere. That "install and go" quality is an infrastructure-level win.
For OpenAI itself, the move positions Codex as the runtime beneath the harness: skill frameworks like Superpowers sit on top, proxy gateways like Sub2API sit below, and the runtime itself does one thing only—put instructions into the filesystem and shell. This "narrow and deep" strategy is more likely to survive than trying to build an all-in-one IDE.
Codex is still in alpha with a fast release cadence; pinning versions for production is the safe choice. But regardless of who wins the broader war, the Rust rewrite has already raised the industry's floor to ~100ms startup. The next time a coding agent feels slow, nobody is going back to Python.
GitHub: github.com/openai/codex (113,312 ⭐, +1,544 stars on 8/22)
*Sources: Smartotics AI Daily Report 8/23, Dev Breakfast Daily Intel 8/23, GitHub Trending 8/23, AppServer protocol docs, issue #37674 (enhancement, closed 8/21), Reddit r/LocalLLaMA discussions.*