There is a specific paradox in the Codex CLI versus Claude Code debate that most comparison posts skip over because it is uncomfortable to explain: developers prefer Codex CLI in daily use, and yet they rate Claude Code’s output higher when they cannot see which tool produced it.
A widely repeated tally of 500+ Reddit developers says 65% preferred Codex CLI day to day, and that blind reviews rated Claude Code’s output cleaner 67% of the time. I could not find the original methodology for either number, so treat them as community anecdote rather than research.
The pattern still matches what I see in my own use, and the explanation matters for how you choose.
What each tool actually is
Codex CLI is OpenAI’s terminal coding agent — open source under Apache 2.0, built in Rust, with about 129,800 stars on the openai/codex GitHub repo in October 2026 and over 400 external contributors as of May 2026. When this post was first written it ran GPT-5.5 or GPT-5.3-Codex; since CLI 0.159.1 the default model is GPT-6.1 Sol. It operates in your terminal and includes OS-level sandboxing (Seatbelt on macOS, bubblewrap and seccomp on Linux, with network access off by default) to limit what it can do without your approval. It is fast, transparent, and you can read the source code if you want to understand how it works.
Claude Code is Anthropic’s terminal agent — closed source, running with a 1 million token context window. In May it ran Claude Opus 4.7; today it runs Claude Opus 5.5 and Claude Sonnet 5.5. It reads your filesystem, writes files, runs commands, and operates autonomously across your codebase. As covered in the full AI tool comparison, Claude Code’s approach to complex multi-file work is distinctly different from IDE tools — it delegates and you review, rather than offering suggestions for you to accept.
Both tools live in your terminal. Both can read your codebase, run commands, and write code. The architecture underneath is fundamentally different, and that difference shows up in specific ways.
The token efficiency gap — and why it matters
The clearest quantitative difference is token consumption. In a Figma-to-code test that Composio’s Rohith Singh published in September 2025, later reused on Morph LLM’s comparison page, Claude Code consumed 6,232,242 tokens while Codex CLI consumed 1,499,455 tokens — roughly a 4x gap on the same task. That was one task and one run, with Claude Sonnet 4 against GPT-5 Medium, so read it as a direction rather than a constant.
At GPT-5.5 API pricing ($5 input / $30 output per million tokens), 1.5 million tokens is meaningfully cheaper than 6.2 million tokens. The efficiency difference is real, and for teams running agents continuously across many tasks, it compounds into substantial monthly cost differences.
Claude Code’s verbosity is intentional — it explains its reasoning, documents its decisions, and narrates what it is doing. This is a feature when a developer is reviewing the agent’s work closely. It is cost without value when the agent’s output goes directly to a test suite or gets merged after a quick diff review.
There is also a reality check from METR. Its July 2025 randomized controlled trial found that 16 experienced open-source developers took 19% longer to finish issues when they were allowed to use AI tools, even though they had predicted a 24% speedup. That study was not about rate limits or Claude Code specifically.
What it does show is that how fast an agent feels and how fast your work ships are different numbers. If you run either tool continuously — queued tasks, CI triggers, overnight autonomous sessions — measure turnaround time instead of trusting the feel.
Benchmarks: where each leads
The benchmark picture is genuinely split, which is why picking a winner is harder than most comparison articles claim.
A note on dates: these May 2026 numbers compare GPT-5.5 against Claude Opus 4.7, and both sets are vendor-reported, taken from OpenAI’s GPT-5.5 announcement as compiled by Vellum. Codex CLI now defaults to GPT-6.1 Sol and Claude Code runs Opus 5.5 and Sonnet 5.5, so treat this section as a snapshot of the two tools in May.
Where Codex CLI / GPT-5.5 leads:
Terminal-Bench 2.0: 82.7% versus Claude Opus 4.7’s 69.4% — a 13-point gap on complex shell workflows requiring planning, iteration, and tool coordination. For DevOps automation, CLI tooling, build pipeline debugging, and anything terminal-native, this matters.
Where Claude Code leads:
SWE-bench Pro: 64.3% versus 58.6% for GPT-5.5 — a 5.7-point gap on resolving real GitHub issues in real codebases. For the kind of work that represents most developer tasking — actual bugs, actual features, actual codebases — Claude Code’s architectural reasoning produces better results more often.
The hallucination rate gap from the GPT-5.5 vs Claude Opus 4.7 comparison is relevant here too: on Artificial Analysis’s AA-Omniscience benchmark, Claude Opus 4.7 had a 36% hallucination rate versus 86% for GPT-5.5. When a terminal agent fabricates an API endpoint, incorrect import path, or nonexistent configuration option, you debug a silent failure. The hallucination rate is not an abstract benchmark — it shows up as time spent chasing problems that the tool introduced.
Why people prefer Codex CLI daily despite rating Claude Code higher
The paradox resolves when you think about what “daily preference” measures versus what “blind code review” measures.
Daily preference reflects the experience of working with the tool — response speed, how it communicates what it is doing, how often it asks for clarification versus proceeding, whether it feels like it is with you or ahead of you. Codex CLI is faster at producing output, more transparent in its sandboxed execution, and — for developers who want to maintain hands-on control — less likely to surprise you by doing something larger than intended.
Blind code review reflects only the artifact: is this code correct, readable, maintainable? In my experience Claude Code produces cleaner, more modular, better-documented code. If the widely quoted 67% blind-review figure holds up, the gap is not close.
The practical implication: if you hand the tool’s output directly to a colleague or into a PR that your team will maintain, Claude Code’s output requires less cleanup. If you are iterating quickly on your own tasks, experimenting, or running high-volume automation where you review output at a coarser grain, Codex CLI’s speed and efficiency is the better fit.
Open source versus closed — the real difference for teams
Codex CLI’s open-source Apache 2.0 license is not just a philosophical preference. It has practical consequences:
Auditability: You can read exactly what Codex CLI does before you run it on a production codebase. For security-sensitive environments, this matters. Claude Code’s behavior is documented but not inspectable at the source level.
Self-hosting and modification: Teams with specific security requirements can run Codex CLI without routing through OpenAI’s servers by pointing it at a self-hosted model. That option does not exist with Claude Code.
Contribution: The 400+ contributors to Codex CLI’s codebase have added integrations, fixed edge cases, and built extensions that OpenAI’s own team did not. This is real value that open-source development compounds over time.
The counterargument is that Claude Code’s closed-source development allows Anthropic to ship tightly integrated features — Agent Teams with coordinated sub-agents and direct messaging between them, a built-in diff viewer, native session management — that open-source coordination cannot match for speed of iteration.
MCP support: where Claude Code still leads
Both tools now support MCP for connecting to external data sources and tools. The difference is maturity and breadth.
Claude Code’s MCP integration has been in production longer and has broader coverage. The MCP servers guide on this blog covers the ecosystem in detail — but the practical version is that Claude Code connects smoothly to Postgres, Figma, Notion, Slack, and the full range of official MCP servers. Codex CLI uses TOML for MCP configuration and has solid support for the core use cases, but the ecosystem integration is less mature.
For teams already running MCP infrastructure, this is a non-trivial difference. The agent that connects to your database, your design tool, and your project management system has significantly more context than one that can only see your filesystem.
The actual cost picture
Both tools start at $20 a month and climb from there for heavy users, though the paths are different.
Codex CLI on ChatGPT plans: Codex is included in ChatGPT plans, according to OpenAI’s Codex pricing page. Plus costs $20/month. Pro starts at $100, Pro 200 reopened on September 29, 2026 with 10x the Plus allowance for new subscribers, and Pro 500 costs $500/month for 25x Plus. Business is $25 per user monthly, or $20 billed annually. If you sign in with an API key instead, you pay per token, and the token efficiency advantage means equivalent work tends to cost less than it would with Claude Code.
Claude Code on Claude plans: Claude Code is included in every paid plan on Anthropic’s pricing page. Pro costs $20/month ($17 billed annually), and Max starts at $100/month for heavier use. API billing is an alternative to a subscription, not a charge on top of it. For teams on API billing, Anthropic’s Claude Code cost docs put the enterprise average at about $13 per developer per active day, or $150–250 per developer per month, with 90% of users under $30 a day.
Which one to use
Use Codex CLI if:
You care about token efficiency and operating cost at scale. You want open-source auditability. Your work is terminal-heavy — DevOps, CLI tools, build automation — where the 82.7% Terminal-Bench lead is relevant. You prefer faster, more transparent agent behavior and are comfortable with slightly lower code quality in the output.
Use Claude Code if:
Code quality and correctness is the primary constraint. You are working on complex multi-file reasoning tasks where SWE-bench Pro leadership (64.3%) matters. You want deeper MCP integration and Agent Teams for parallel sub-agent workflows. You are comfortable with higher token consumption in exchange for cleaner output and more reliable long-horizon task completion.
The most common professional setup: Codex CLI for speed-sensitive daily tasks and high-volume automation. Claude Code for complex feature work, large-codebase refactors, and anything that goes directly to a colleague for review. The tools are genuinely complementary — running both, each on a mid-tier plan, is a real setup for teams where the productivity return justifies it.
Token efficiency figures from Composio’s Figma-to-code test (September 2025), also cited by Morph LLM. METR productivity finding from METR’s July 2025 randomized controlled trial. Terminal-Bench 2.0 and SWE-bench Pro figures are vendor-reported from OpenAI’s GPT-5.5 announcement (April 2026). The Reddit preference and blind-review figures are widely repeated but could not be traced to an original methodology. Codex CLI star count from github.com/openai/codex as of October 2026.
(Updated October 19, 2026: corrected the METR finding, which was a July 2025 study showing 16 experienced open-source developers were 19% slower with AI tools, not a measure of Claude Code rate limits; corrected Claude Code pricing, which is included in Claude Pro at $20/month ($17 annual) with Max from $100, not $20 plus API usage on top; removed the cost figures wrongly attributed to METR and replaced them with Anthropic’s published averages; updated Codex plan prices (Plus $20, Pro from $100, Pro 200, Pro 500 at $500) and removed the expired May 31 promotion; corrected the Linux sandbox to bubblewrap and seccomp; re-attributed the Figma token figures to Composio’s September 2025 test with Claude Sonnet 4 and GPT-5 Medium; attributed hallucination rates to Artificial Analysis; marked the Reddit and blind-review figures as unverified; and noted current default models, GPT-6.1 Sol for Codex CLI and Claude Opus 5.5 / Sonnet 5.5 for Claude Code.)