The Real Cost of AI Coding Assistants in 2026

Ask an engineering lead what their AI coding tools cost and you usually get the sticker price back: twenty dollars a head, give or take. Ask to see the actual bill and the number is often higher. The reason is rarely a hidden fee. It is that the flat seat is only the entry door, and almost every assistant meters real usage on top of it.

This article does not rely on any private dataset. It uses two public, checkable inputs: the vendors’ own published pricing (mirrored in the ByteCosts subscription index, checked 2026-06-06) and a clearly labeled cost model built from published API rates. Everything you can recompute, we show the arithmetic for.

What each plan actually charges for a seat

These are the published self-serve prices, from each vendor’s pricing page, as tracked in the ByteCosts subscription index on 2026-06-06.

The seat is the floor, not the bill. The next section is where the real money moves.

What the plans actually meter

Each vendor’s published pricing page is explicit that the paid seat includes a fixed amount of model usage, after which you pay more.

• Cursor. Every plan includes a set amount of model usage; on-demand usage continues after the included amount is consumed and is billed in arrears (cursor.com pricing). The $20 Pro plan is an included usage pool, not unlimited frontier-model access.
• GitHub Copilot. Pro includes unlimited completions plus 300 premium requests a month; Pro+ includes 1,500. Premium-request overage is billed at $0.04 per request on every paid plan (github.com Copilot plans). GitHub has also announced a move to usage-based AI-credit billing, which makes the seat-versus-usage split even sharper (github.blog).
• Windsurf and Claude. Both price higher tiers as multiples of a base usage allowance (Windsurf Pro to Max, Claude Pro to Max 5x and Max 20x), which is the same pattern in different words: the seat buys a quota, heavy use buys more quota.

The practical takeaway: a single advertised seat price tells you the minimum, and the three things that push real cost above it are context-window size per request, background agents and autocomplete that run constantly, and the three to seven iteration rounds a hard task takes. None of those are line items you see at signup.

A modeled heavy month (illustrative, not measured)

To show the gap between seat and usage, here is a modeled scenario. It is not a measured bill from any team. It prices an agentic coding workload on published API rates so you can reproduce or adjust every number.

Assumptions: a coding harness running Claude Sonnet 4.6 at its published rate of $3 per million input tokens and $15 per million output tokens (ByteCosts model index, 2026-06-06). Each task loads context and runs several full-context iterations. The token assumptions below sit inside a 40,000 to 90,000 input-tokens-per-task range typical of agentic sessions.

The math for the heavy row, over a 22-day month: each task uses 60,000 input tokens times 4 iterations, which is 240,000 input tokens, plus 4,000 output tokens times 4, which is 16,000 output tokens. At the published rates that is 240,000 divided by one million times $3 (72 cents) plus 16,000 divided by one million times $15 (24 cents), so about 96 cents per task. Ten tasks a day across 22 days is roughly $211. The light row, computed the same way, lands near $12, comfortably inside a $20 seat. The point is not the exact figure. It is that the same person can sit anywhere on this curve, and the seat price only describes the bottom of it.

Does it pay for itself? The honest answer is contested

Earlier versions of this kind of article quoted confident productivity gains. The public evidence does not support a single clean number, and in one well-run study it points the other way.

• A randomized controlled trial by METR had 16 experienced open-source developers complete 246 real issues, with AI allowed or disallowed per issue. Developers expected AI to make them about 24 percent faster; it actually made them about 19 percent slower on these mature codebases, even though the primary tool was Cursor Pro with Claude Sonnet (metr.org, paper arxiv 2507.09089).
• Google’s 2025 DORA report, a much larger survey, finds AI adoption near 90 percent and a majority reporting productivity gains, but also roughly 30 percent who distrust AI-generated code, and it frames AI as an amplifier that raises both delivery throughput and instability (dora.dev DORA report 2025).

Read together, the honest position is that returns depend heavily on the codebase, the task, and the operator’s experience with the tool. Treat productivity as something to measure on your own work, not a number to assume.

How to keep the bill honest

1. Measure before you scale. Run a short, real trial with time tracking instead of assuming a percentage gain.
2. Default routine work to a cheaper model. Claude Haiku 4.5 lists at $1 per million input tokens versus Sonnet 4.6 at $3 (ByteCosts model index), so reserving the frontier model for genuinely hard logic changes the curve above, not just the sticker.
3. Set a per-engineer monthly budget and watch the usage meter, not only the seat count.
4. Audit subscriptions each quarter. Overlapping Cursor, Copilot, and a personal Claude plan is easy to accumulate and easy to forget.

AI coding tools are genuinely useful and genuinely metered. The teams that stay in control are the ones treating the seat as a floor and the usage meter as the real line item.

Sources and method

What is measured here: every seat price and metering rule is a published vendor fact, taken from the vendor’s own pricing page and mirrored in the ByteCosts subscription index (generated 2026-06-06). The model rates are from the ByteCosts model index (2026-06-06). What is modeled: the light, median, and heavy monthly figures are an illustrative scenario priced on those published rates with the stated token and iteration assumptions; they are not a measured bill from any team. Productivity claims are quoted from named public studies, not from ByteCosts data.

• Cursor pricing (cursor.com), accessed June 9, 2026
• GitHub Copilot plans (github.com), accessed June 9, 2026
• GitHub Copilot usage-based billing announcement (github.blog), accessed June 9, 2026
• Windsurf pricing (windsurf.com), accessed June 9, 2026
• Tabnine pricing (tabnine.com), accessed June 9, 2026
• Claude pricing (claude.com), accessed June 9, 2026
• Anthropic model pricing (platform.claude.com), accessed June 9, 2026
• METR randomized trial on AI and experienced developer productivity: metr.org study and paper, accessed June 9, 2026
• DORA 2025 State of AI-assisted Software Development (dora.dev), accessed June 9, 2026
• ByteCosts subscription index and model index, datasets in this repository, generated 2026-06-06. See the Provider Pricing Index and price change ledger.