Cursor vs Codex vs Claude Code for $20: which plan gives the most usable coding time?

At $20 per month, Codex is the best current pick for raw agentic coding volume, while Cursor Pro stretches furthest for developers who count autocomplete and short IDE interactions as useful work. Claude Pro is the hardest to recommend when quota alone is the decision: its five-hour and weekly limits are less predictable, although its separate Agent SDK credit changes the math for scripted use. There is no defensible universal request count because the three products meter different things. Our July 28, 2026 normalization test shows exactly why: Cursor exposes a dollar-denominated monthly pool, Codex exposes token-to-credit rates but not a fixed public Plus allowance, and Claude exposes time-window limits without a subscription token conversion.

That answer is deliberately narrower than our broader Claude Code vs Cursor workflow comparison. Here, “most usage” means the most useful coding work before the included allowance blocks you or asks for more money—not which model writes the best code.

The short answer by workload

Your main workload	Best $20 choice	Why
Long local agent tasks, refactors, and debugging	Codex with ChatGPT Plus	The current Plus offer includes Codex and temporarily advertises 2× rate limits; recent user reports consistently place its raw ceiling above Claude Pro.
Autocomplete, inline edits, and many small IDE interactions	Cursor Pro	Unlimited Tab completions do not compete with the metered agent pool, and the agent budget is the easiest of the three to inspect.
Claude chat plus occasional interactive coding	Claude Pro	One subscription covers Claude and Claude Code, but they share limits. Buy it for the Claude workflow, not for a promised task count.
Scripted claude -p or Agent SDK experiments	Claude Pro, with a caveat	Eligible Pro users can claim a separate $20 monthly Agent SDK credit; this is distinct from interactive Claude Code usage.
A single hard task where completion matters more than quota	Choose by harness, not quota	Our Codex vs Claude Code agent-loop test is the more relevant comparison.

The Codex recommendation is time-sensitive. OpenAI describes the 2× limit as available “for a limited time,” so it should not be treated as a permanent plan entitlement.

What each $20 subscription actually buys on July 28, 2026

The monthly prices below are US list prices before local taxes. API billing is separate unless explicitly noted.

Plan	Published price	Included coding access	Meter that matters	What happens at the edge
Cursor Pro	$20/month	Unlimited Tab completions, frontier-model access, agent features	At least $20 of API-priced agent usage plus additional bonus usage	Buy additional usage or upgrade
ChatGPT Plus + Codex	$20/month	Local Codex clients and cloud access where available	Shared agentic allowance; usage maps to model input, cached-input, and output credits	Wait for reset or add credits where available
Claude Pro + Claude Code	$20/month	Claude chat, Claude Code, and Cowork	Five-hour session limit plus a weekly limit shared across Claude products	Wait, upgrade, or enable usage credits

This table corrects two common but stale simplifications.

First, old Cursor articles often say “500 requests” or “unlimited Auto.” Cursor’s current documentation instead describes an API-priced agent pool plus bonus usage. It gives median-user estimates—about 225 Sonnet 4, 550 Gemini, or 500 GPT-5 requests on Pro—but those are examples, not guaranteed exchange rates. Model choice and context size still change the burn rate. For the complete IDE value proposition, see our current Cursor review.

Second, neither Codex nor Claude Pro sells a fixed public number of coding prompts. OpenAI says task cost varies with model, repository size, context, and run length. Anthropic says Claude Pro resets its session allowance every five hours and also applies a weekly limit. Anyone promising an exact “X prompts per month” without showing an account dashboard is converting a personal workload into a universal rule.

TopInsight test: normalize the meters before comparing them

• Test date: July 28, 2026
• Environment: Windows 11 64-bit (10.0.26200), Node.js 24.16.0, Codex CLI 0.142.5, Claude Code 2.1.178
• Test type: deterministic pricing normalization, not a model-quality benchmark
• Synthetic task shape: 100,000 uncached input tokens, 400,000 cached input tokens, and 10,000 output tokens

We chose a deliberately context-heavy profile because agentic coding repeatedly sends repository context and benefits from caching. The numbers are not meant to represent an “average feature.” They are a fixed ruler that anyone can rerun when vendor rates change.

const task = { inputM: 0.1, cachedM: 0.4, outputM: 0.01 };

const cursorAutoUsd = task.inputM * 1.25 + task.cachedM * 0.25 + task.outputM * 6;

const codexSolCredits = task.inputM * 125 + task.cachedM * 12.5 + task.outputM * 750;

const codexTerraCredits = task.inputM * 62.5 + task.cachedM * 6.25 + task.outputM * 375;

console.log({
  cursorAutoUsd,
  cursorTasksPer20Usd: 20 / cursorAutoUsd,
  codexSolCredits,
  codexTerraCredits,
});

Reproduced result

Meter	Cost for the fixed task	What can be calculated
Cursor Auto published rates	$0.285	About 70 such tasks consume a $20 pool, before any bonus usage
Codex GPT-5.6 Sol rate card	25 credits	Exact task credit cost, but not the number of included Plus credits
Codex GPT-5.6 Terra rate card	12.5 credits	Half the Sol credit burn for the same token shape
Interactive Claude Code on Pro	Not published as tokens or dollars	No honest conversion from a five-hour window to task count

This is the most important finding in the comparison: only Cursor lets us turn the public $20 agent pool into a task estimate. Codex makes model efficiency visible but does not publish a stable Plus credit balance on the cited plan page. Claude does not publish a token conversion for its included interactive allowance at all.

The test also shows why model selection matters. On the same token profile, Codex Terra consumes half as many credits as Sol. That does not mean Terra completes the same work at the same quality; it means a user can trade model capability for more attempts. A request counter that ignores the selected model is not a usable purchasing metric.

We did not run a quota-exhaustion benchmark. It would require three fresh accounts, synchronized renewal and reset windows, identical repository history, and enough repeated paid work to hit every wall. Our test machine also did not have a Cursor agent client installed. Claiming a three-way “firsthand” exhaustion result from that environment would be misleading.

What Reddit reports—and what the videos miss

The exact question appears repeatedly in current community discussions. In the June 2026 r/cursor thread asking which $20 plan gives the most usage, the useful replies separate three ideas that are often collapsed:

• Cursor’s first-party Composer/Auto path can stretch much further than choosing expensive frontier models manually.
• Codex is commonly described as the largest raw autonomous-work ceiling, especially at lower reasoning settings.
• Claude Code can produce excellent results but long sessions compound context and can hit the rolling window quickly.

A May r/ClaudeCode thread adds a concrete counterexample: one heavy user reported burning through Codex’s five-hour limit quickly, then preferred Cursor after a week because Composer handled sustained work more comfortably. That is not proof that Cursor universally wins; it is evidence that “number of tasks” depends on whether the task is interactive editing or long-horizon agency.

The July 24 Claude Code discussion still reports Codex as more generous in practice, but another fresh thread from July 26 contains users frustrated by Codex’s weekly limit. Community reports therefore support our current Codex recommendation without turning it into a guaranteed quota.

The three independent videos we reviewed are better at showing workflow than billing. Theo’s three-way comparison explains the products’ different design philosophies; Your Average Tech Bro demonstrates how each surface changes daily work; Jan Marshal gives all three the same app brief. They help answer what kind of work feels useful. They do not expose a reproducible subscription allowance, so we do not use their impressions as pricing facts.

That gap is also consistent with a 2026 task-stratified study of 7,156 agent-generated pull requests: no agent won every task category. A quota comparison without workload categories hides the variable that matters most.

When Cursor Pro gives you more usable work

Choose Cursor Pro if most of your AI interactions are:

• Tab completion while you continue writing the code;
• small inline edits with rapid visual diff review;
• codebase questions inside a VS Code-style editor;
• frequent short agent runs where interface friction matters.

Unlimited Tab completions are the decisive accounting advantage. A day full of completions can create value without touching the agent pool. Neither Claude Code nor Codex offers the same first-party completion product in its $20 subscription.

The tradeoff is frontier-model usage. Cursor meters manually selected models at their inference price, so a handful of long, output-heavy runs can consume more of the monthly pool than dozens of small edits. If you expect the subscription to subsidize continuous Opus-class agent work, buy from the model provider or use Codex rather than assuming Cursor will absorb the cost.

When Codex Plus gives you more usable work

Choose Codex with ChatGPT Plus if you want:

• long local implementation or debugging runs;
• a terminal, IDE extension, desktop app, and cloud delegation under one account;
• the option to select a cheaper model or reasoning level for routine work;
• the largest current raw agentic allowance signaled by both the temporary 2× offer and recent user experience.

There are two qualifications. The allowance is shared with other agentic OpenAI features when they are available on your plan, and OpenAI can end the 2× promotion. Also, the current rate card makes output substantially more expensive than cached input: verbose or churn-heavy agents consume more credits even when they inspect the same repository.

For a broader tool assessment—not just quota—read our Codex CLI review.

When Claude Pro is still the right $20 choice

Claude Pro makes sense when Claude itself is the product you want and Claude Code is an included coding surface. It remains attractive for:

• planning and architecture discussions that continue naturally into implementation;
• developers who prefer Claude Code’s terminal harness;
• occasional coding alongside substantial general Claude use;
• eligible scripted Agent SDK work that can use the separate monthly credit.

The separate credit needs careful wording. Since June 15, 2026, eligible subscribers can claim a monthly Agent SDK credit; Pro receives $20. Anthropic says claude -p and Agent SDK usage draw from that credit rather than the interactive subscription allowance. Interactive Claude Code still consumes the shared five-hour and weekly limits. This does not make normal terminal sessions “another free $20.”

Anthropic also doubled Claude Code’s five-hour limits and removed peak-hour reductions on May 6. Those are meaningful improvements, but the company still does not publish a stable prompt count. If predictable quota is your primary criterion, Claude Pro remains the hardest plan to model.

Final verdict

If you force us to choose one $20 subscription on July 28, 2026:

1. Pick Codex Plus for the most raw agentic coding work right now.
2. Pick Cursor Pro for the most total IDE utility and the clearest monthly agent budget.
3. Pick Claude Pro when you specifically want Claude’s model and harness, not because its quota is easiest to predict.

The practical purchasing rule is simple: first classify your work as completion-heavy, agent-heavy, or reasoning-heavy. Then compare the meter that applies to that work. “How many prompts do I get?” is the wrong question because these three products do not sell the same unit.

Recheck the official pricing and usage pages before subscribing. The conclusion can change as soon as OpenAI ends its 2× promotion, Cursor changes bonus capacity, or Anthropic revises its rolling and weekly limits.