Codex vs Claude Code usage limits in 2026 — same rules now, very different mileage

A recurring thread on r/codex this month — hundreds of upvotes — carries some version of the same line: the usage limits on Codex compared to Claude Code are absurd. Not absurd-bad. Absurd-good: people describe getting far more coding done on a $20 Codex plan before anything stops them than they get out of Claude Code at the same price. It’s a real, repeatable observation. But the popular explanation — “Codex just has more generous limits” — is the wrong lesson, because by mid-2026 the two products have almost the same limit machinery. The difference lives one level down, in how fast each tool spends the quota it’s given.

This page lays out both systems side by side, tier by tier, and explains the part the “more generous limits” framing skips: why an identical-shaped wall arrives sooner on one side. Sources are at the end.

The 30-second version

1. The rules converged. Both now run a rolling 5-hour window + weekly caps + token-metered credits + paid overflow. Claude Code has worked this way through 2026; Codex adopted token metering on April 2, 2026. On structure, they’re near-twins.
2. So limits aren’t the axis. With the same machinery, what differs is throughput per dollar — how much work you get before the meter runs out.
3. Claude Code spends faster. Independent comparisons put its token use at several times Codex’s on identical tasks (~4x in one long test). More tokens per task = the token-metered quota empties sooner.
4. Two multipliers make it worse on Claude’s side. Opus drains the pool far faster than Sonnet, and Claude’s meter is shared with Claude chat. Codex’s coding usage is metered on its own plan with frugal defaults.
5. Mind the name trap. Anthropic Pro = $20. OpenAI Pro = $100–$200; its $20 plan is Plus. Compare Plus vs Pro at $20, or you’re off by 10x.

The rules are now nearly identical

For most of the debate’s history, Codex and Claude Code had genuinely different limit designs. That gap has closed. Here is the machinery on each side today:

They even landed on the same shape of honesty problem: because both meter tokens rather than counting messages, neither can tell you how many prompts you get. OpenAI publishes ranges — Plus is listed at roughly 15–80 GPT-5.5 local messages per 5-hour window (wider for lighter models) — precisely because the true unit is tokens, and a heavy task eats several light ones’ worth. Claude expresses its limits as multipliers relative to Pro rather than message counts, for the same reason. If a comparison hands you a crisp “X prompts vs Y prompts,” be skeptical; the vendors themselves won’t.

The tiers line up — including a trap

Once you get the names right, the paid tiers map onto each other almost one-to-one. The trap is that “Pro” means opposite things: on Anthropic it’s the cheapest plan; on OpenAI it’s the most expensive coding tier. The $20 plan on the OpenAI side is Plus.

Both express the step-up in the same language — 5× and 20× the entry rate — at the same two price points. So the honest matchup at the price a solo developer actually pays is Codex Plus vs Claude Code Pro, both $20. Pit “Codex Pro” against “Claude Pro” and you’re comparing a $200 plan to a $20 one, which is where a lot of “Codex is so much more generous” and “Codex is way pricier” takes both quietly go wrong. (List prices; both vendors changed these more than once in 2026 — treat the table as a snapshot, not a contract.)

Same wall, reached sooner: why

If the rules match, why do people hit the wall faster on Claude Code? Three things stack:

1. Token efficiency. This is the big one. In independent hands-on comparisons, Claude Code consumes markedly more tokens than Codex to complete the same task — one widely-cited 100+ hour comparison landed near 4x. Under token-based metering, tokens are the quota, so 4x the tokens is roughly 4x the burn for the same result. Crucially, this isn’t Claude wasting effort: the extra tokens correlate with more exploration, more verification, and more deterministic output. It’s a genuine tradeoff — thoroughness you pay for in quota — not a defect. But it fully explains why the identical-shaped meter drains faster.

2. Model drain. Within Claude Code, model choice swings burn rate hard: Opus draws down the pool far faster than Sonnet. A developer who leaves Opus on for routine work will empty a Max allocation in a way a Sonnet user won’t — and Claude’s weekly cap is further carved up by model (Opus and Sonnet draw at different rates, and Fable 5 has carried its own temporary weekly sub-cap since its July restoration). Codex’s default coding models are comparatively frugal, so the naive setting costs less.

3. The shared pool. Anthropic’s meter is shared across Claude chat and Claude Code — a heavy coding afternoon also spends your chat allowance, and vice versa. Codex meters coding usage on its own coding plan. Same nominal budget, but on Claude’s side more activities compete for it.

None of these is a limit rule. They’re all reasons the same rule bites differently — which is exactly why “just compare the limits” misses it.

So who should pick which

• Optimizing for runway at $20? Codex Plus. For heavy iteration, experimentation, or high-volume routine edits, it gives more room before the wall — the real substance behind the r/codex enthusiasm.
• Want Claude Code’s thoroughness, or already in the ecosystem? Claude Code, with eyes open: prefer Sonnet for routine turns, save Opus for the hard problems, and remember the shared pool and weekly caps. The May 2026 doubling means the money buys roughly twice the agent time it did in the spring.
• On $100–$200 either way? Both tiers target the all-day user. Decide on output quality, model lineup, and ecosystem fit — the quota stops being the deciding factor up here. The cross-vendor verdict and the Claude-vs-ChatGPT coding breakdown are the better lens.
• Either way, cut the burn at the source. The cheapest quota win on Claude’s side is generating less code to begin with — over-engineering rules in CLAUDE.md report meaningfully fewer tokens on identical tasks, which is burn you never spend.

The real lesson

The interesting thing about “Codex vs Claude Code limits” in 2026 is that it has quietly stopped being a question about limits. Two competitors watched each other and converged on the same design — 5-hour window, weekly caps, token credits, paid overflow — until the rules are close to a wash. What’s left is efficiency: how many tokens a tool spends to do your task, and how a shared pool and an expensive default model multiply that. Codex feeling “more generous” is mostly Codex being more frugal, and Claude Code feeling tight is mostly Claude Code being more thorough. Which one you want depends on whether you’re paying for runway or for rigor — and now that the meters match, that’s finally the only question worth arguing about.

Companion reading

• Claude Code usage limits, explained — the 5-hour window, weekly caps, and how to watch your burn
• Claude Code pricing in 2026 — which Claude tier the math actually favors
• Best AI coding agents, 2026 verdict — where Codex and Claude Code land head to head
• Claude vs ChatGPT for coding — the broader capability matchup behind the quota
• Stop your CLAUDE.md over-engineering — cut the token burn that pushes you into the caps

Sources

1. Codex rate card — OpenAI Help Center
2. Codex pricing — OpenAI
3. What is the Max plan (usage limits) — Anthropic Support
4. Higher limits for Claude Code (May 6, 2026) — Anthropic
5. Claude Code vs OpenAI Codex, 100+ hours compared — Composio
6. OpenAI Codex Pricing 2026: Plans, Credits, Rate Card — UI Bakery

FAQ

Does Codex or Claude Code have more generous usage limits in 2026? At $20, developers consistently report Codex (Plus) giving more coding runway before a limit than Claude Code (Pro). But the two share almost identical limit structures now — 5-hour window, weekly caps, token credits — so the difference is throughput, not rules: independent comparisons report Claude Code using several times more tokens than Codex on identical tasks (~4x in one long test), so it drains the same-shaped quota faster. Claude’s higher token use correlates with more thorough output, but you meet the wall sooner.

How do the limits actually work? Nearly the same way. Claude Code: a 5-hour session window resetting every five hours, plus weekly caps resetting seven days after a session starts, shared across Claude chat and Claude Code, with Usage-credit overflow at API rates. Codex (since April 2, 2026): local messages and cloud tasks share a 5-hour window with weekly limits, priced in credits per million tokens, overflow via purchased credits. Both meter tokens, so neither promises an exact prompt count.

Is Codex Pro the same as Claude Code Pro? No — confusing them is a 10x mistake. Anthropic Pro is the $20 entry plan; OpenAI Pro is the top coding tier at ~$100 (5×) to $200 (20×), and its $20 plan is Plus. The fair $20-vs-$20 comparison is Codex Plus vs Claude Code Pro. Higher tiers align: Codex’s 5×/20× sit at the same ~$100/$200 as Claude’s Max 5× and Max 20×.

Why do I run out of Claude Code faster on the same price? Three reasons stack: token efficiency (Claude Code uses several times more tokens per task, burning a token-metered quota faster), model drain (Opus draws down Claude’s pool far faster than Sonnet), and the shared pool (Claude chat and Claude Code spend the same meter). Codex meters coding on its own plan with more frugal default models.

Should I switch to Codex for the limits? If your constraint is runway at $20, Codex Plus gives more room — a real reason people switch. If you value Claude Code’s thoroughness, are in the Claude ecosystem, or run on Max (where the May 2026 doubled limits and Opus quality pay off), Claude Code is still worth it; you just manage the burn. At $100–$200 both target the all-day user, so decide on output quality and ecosystem, not quota. And both vendors revised these limits repeatedly in 2026 — treat any number as a snapshot.