The honest answer: the four leading coding agents are close enough on quality that the benchmark shouldn't decide it — the pricing model should. If you want a flat, forecastable bill under heavy daily use → Claude Code (Max tiers). Lowest entry price and the broadest IDE plus issue-to-PR reach → GitHub Copilot. You live inside a dedicated editor and want parallel background agents → Cursor. You already pay for ChatGPT and want it all on one bill → OpenAI Codex. That's the decision. The rest of this is why the benchmark is a trap and how each one actually charges you.

Why the leaderboard is the wrong axis#

Open any "best coding agent" roundup and you'll find a SWE-bench Verified table with one tool on top. Open another from the same week and a different tool is on top. One late-2026 comparison cites Claude Code at 88.6% on SWE-bench Verified and Codex at 82.7% on Terminal-Bench — different benchmarks, different winners, and both are single-source snapshots that will have moved by the time you read this.

For the overwhelming majority of real codebases, the top four are peers. The gaps are within noise, and they leapfrog on a monthly cadence that no purchasing decision should try to track. Choosing your daily driver on a two-point benchmark delta is like choosing a laptop on a single Geekbench run: it measures something real and tells you almost nothing about the thing you'll feel every day.

The thing you'll feel every day is the bill. And the bills are shaped very differently — not in sticker price, where most entry tiers cluster between $10 and $20 a month, but in how each tool meters the work.

The four pricing models, plainly#

Claude Code — flat tier, rolling windows. The Max tiers ($100 and $200/month) are flat-rate, which is the appeal: a predictable number regardless of how hard you lean on it in a given week. The catch is that usage counts against rolling time windows, so very heavy bursts can throttle you until the window rolls. You can also run it pay-as-you-go against the API. The shape: predictable monthly cost, occasional rate-limit friction, best when your usage is high and steady.

GitHub Copilot — cheap seat plus metered credits. Copilot wins the entry price — a Free plan, Pro around $10, Pro+ at $39, Max at $100 for individuals — but the agentic work rides on a pool of AI credits bundled with the seat (the Business seat, around $19, reportedly now includes about $19 of credits). Heavy agent runs exhaust that pool, and then you're into overage. The shape: lowest floor, but the real cost scales with how much autonomous work you push through it.

Cursor — subscription plus usage in arrears. Cursor's Pro tier is ~$20, but usage is metered on top of the subscription and billed in arrears — meaning a heavy month lands as a bill after you've spent it, which takes active attention to forecast. The shape: great editor-native experience with parallel background agents, variable cost that rewards teams who watch their dashboards.

Codex — it rides your ChatGPT plan. Codex's limits are generally tied to your ChatGPT plan (Plus at $20 and up), with API workloads priced per token on top. If your team already pays for ChatGPT, the marginal cost of adding Codex is low and the billing is one you already understand. The shape: cheapest incremental add if you're already in the OpenAI ecosystem.

The one new capability worth noting#

The only recent change that actually shifts a decision is on the Copilot side: GitHub's October 28 Universe changelog gave its cloud agents session continuity — start a run on your phone, steer it from VS Code, check it from github.com, one session on GitHub-hosted compute throughout. That deepens Copilot's genuine edge: issue-to-PR, cross-surface, cloud-run agents. The caveat, which we unpack in this morning's Wire, is that the announcement shipped no pricing, quota or retention terms — so it strengthens the capability column without clarifying the cost column, which is exactly the column that should decide this.

The leaderboards are peers that leapfrog monthly. The pricing models are durable and shaped completely differently. Choose the one you can forecast, not the one that won last week's benchmark.

How to actually choose#

Model one real week of your own usage, then match it to a meter:

If you're choosing between terminal CLIs specifically, we go deeper in Claude Code vs Codex CLI vs Gemini CLI. But the meta-point holds across all of them: the benchmark is a photo finish that reshoots every week, and the pricing model is the thing that's still true next quarter. Pick the meter you can live with, and let the leaderboards fight it out without you.