OpenAI Codex overtakes Claude Code

The headline feature in Codex CLI 0.128.0 is /goal, and the mechanics are surprisingly humble. According to Simon Willison's teardown, /goal works by automatically injecting two markdown prompt files — goals/continuation.md and goals/budget_limit.md — at the end of every conversational turn. The continuation prompt nudges the model to keep working; the budget prompt tells it when to stop. That's the Ralph loop pattern that hobbyist developers have been hand-rolling for over a year, now wrapped in app-server APIs, persisted state, and TUI controls for create, pause, resume, and clear. Greg Brockman's framing of it as 'Ralph loop++' was unusually candid about the lineage.

What changes for users is the unit of work. Instead of typing a prompt, watching Codex execute, and then prompting again, you give the agent a goal — 'add SSO to this Django app and ship a passing PR' — and walk away. Codex plans, executes, runs tests, refines, and continues until either the goal evaluates as complete or the token budget is exhausted. The TUI lets you pause and resume a long-running goal across days. This is the concrete shape of the 'autonomous senior-engineer' marketing line: not a smarter single response, but a process that doesn't need you in the loop at all.

The 'Codex overtakes Claude Code' framing is doing a lot of work. The clearest signal supporting it is usage: Codex weekly active users hit 3 million in April 2026, up 6x since the start of the year and surpassing two million only a month earlier. The clearest signals against it are money and code quality. Claude Code's annualized run rate exceeded $2.5B in February versus Codex's estimated $1B+, and Claude Code still processes roughly 135,000 GitHub commits per day — about 4% of all public GitHub commits, with SemiAnalysis projecting that to reach 20% by year-end. On benchmarks the picture splits cleanly: GPT-5.5 leads Terminal-Bench 2.0 (82.7% vs Opus 4.7's 69.4%), while Opus 4.7 leads SWE-bench Pro (64.3% vs 58.6%) — terminal automation versus harder real-world software engineering tasks.

The community read tracks this nuance. Reddit's r/codex hosts a 902-upvote post arguing that Codex 5.5 / xhigh 'actually finishes tasks Claude would bail on,' and a thriving setup ecosystem (awesome-codex-skills, agent-orchestrator, ccusage) is forming around it. But the same threads carry contrarian voices flagging astroturfing concerns and developers migrating back to Claude Code, citing the maturity of subagents and hooks. On YouTube, the dominant emerging narrative is hybrid: Claude Code generates, Codex reviews — a divided workflow rather than a replacement. As one X commentator put it, Claude could keep the revenue lead even if Codex overtakes in usage, given how meager the Opus rate limits are.

Behind the pricing aggression is a token-economics story that explains why OpenAI can offer 5x usage at $100. On identical tasks, Claude Code uses roughly 4x more tokens than Codex, and GPT-5.5 generates 72% fewer output tokens than Opus 4.7. A YouTube creator's Figma-to-code experiment captured the gap concretely: Codex CLI consumed about 1.5M tokens versus Claude Code's 6.2M for the same task. When your model is structurally cheaper to run per task, you can sell aggressive plan limits without lighting margin on fire — and you can credibly claim 'more coding capacity per dollar across paid tiers,' as OpenAI did at the Pro launch.

That asymmetry is what makes the April 9 / April 30 one-two punch coherent rather than reckless. The Pro tier's 10x promotional Codex multiplier (running through May 31) is a customer-acquisition lever priced off a cost base Anthropic doesn't have. Then /goal raises the ceiling on how much value those tokens can produce by letting a single user stretch one session across days of autonomous work. Anthropic's counter is harder: Opus 4.7 wins on the harder benchmark, but each task it runs is more expensive to serve, which is exactly why r/codex threads describe Claude's $20-tier limits as 'insane' relative to what Codex Free now provides. The risk for Anthropic isn't that Codex is better — it's that Codex is cheaper to use heavily, and heavy use is what generates the GitHub commit and revenue compounding.

One detail from the r/codex community deserves more attention than it has received: the /goal feature can silently rack up surprise top-up charges. A widely-shared post from a user running /goal reported 43 unexpected top-up charges with no CLI warnings before each one fired. The activation flag is buried in config — [features] goals = true in config.toml — and once enabled, an autonomous loop running for hours or days will draw from whatever auto-top-up policy the account has configured without surfacing the cumulative spend in the TUI. The community workaround is blunt: turn off auto top-up before using /goal.

This is the predictable downside of productizing the Ralph loop. Hand-rolled loops are written by people who already understand the cost model; a CLI flag invites users who don't. The same property that makes /goal compelling — it doesn't ask you to confirm at each step — is what makes the billing surface dangerous when paired with auto top-ups. Until OpenAI ships an in-loop spend visualization or a soft-cap below the budget exhaustion limit, the prudent path for new users is to scope each goal with a hard token budget at creation time and disable account-level top-ups, not rely on the loop's self-evaluation to stop in time.