Cursor’s pricing looks simple until you actually try to predict your bill, and that gap between “$20/mo” and what you pay in practice is the whole story of this plan structure.
Here’s what the four consumer tiers actually buy you. Hobby is free and needs no credit card. You get limited Agent requests and limited Tab completions, enough to decide if the editor fits your workflow, not enough to build anything real. Pro is $20/mo and includes two separate usage pools: one for third-party models — what Cursor’s docs call “Other Models,” billed at each model’s own API rate — and a more generous one for Cursor’s own models (Grok 4.6, Grok 4.5 and Composer 2.5), plus unlimited Tab completions. Pro Plus is $60/mo and Ultra is $200/mo.
How much usage those tiers actually include is the thing Cursor stopped telling you. Until recently the docs put a dollar figure on the Other Models pool — $20 on Pro, $70 on Pro Plus, $400 on Ultra. As of August 30, 2026 that table lists both pools as “Included” with no amount, and the tiers are described by Agent limits instead: Pro Plus gets “3x Pro limits on Agent,” Ultra “20x Pro limits on Agent.” The prices didn’t move; the number you could budget against went away. Cursor’s own usage guidance is now the closest thing to a figure, and it’s a range, not an allowance.
The part that trips people up is what “usage” actually means. Tab completions are unlimited on every paid plan, but Auto is metered now, and since late August every Auto mode bills at the list price of whichever model the request is routed to (the old flat $1.25 in / $6 out rate lasted on Enterprise until September 7, 2026, and is now gone). One more thing the dashboard won’t tell you anymore: since July 31 the Usage page shows tokens, not dollars, on every self-serve plan. The Other Models pool drains when you manually pick a third-party frontier model (Claude, GPT, Gemini), at that model’s real API rate. Route a big agentic task through a top-tier reasoning model — Fable 5.1 at $10 in / $50 out per million tokens, say — and a day’s work costs real money. Lean on Cursor’s own models and Auto’s cheaper setting for routine work, save manual model selection for the moments you actually need a specific model’s judgment, and the included pools stretch much further.
That distinction wasn’t always clear, and it caused a real mess. In June 2025, Cursor retired its old request-counting system (roughly 500 “fast” requests a month, with pricier models like Sonnet counting as two requests) in favor of the credit-pool model described above. The pitch was “unlimited usage” on Pro, but that unlimited claim applied only to Auto mode, not to manually selected models, and Cursor didn’t communicate the difference clearly at launch. Subscribers who kept hand-picking premium models the way they always had ran up unexpected overage charges. By July 4, 2025, Cursor posted a public apology taking “full responsibility” for the unclear rollout and issued refunds for surprise charges billed during the weeks after the switch. If you evaluated Cursor’s pricing before mid-2025 and haven’t looked since, treat that old mental model as void. The request-count era is gone, and everything now runs on dollar-denominated pools — and the “unlimited” label has kept narrowing since: as of July 2026 it applies to Tab completions, not to Auto (see the changelog entry above).
One more line item: Bugbot, Cursor’s automated code-review bot, ships on all paid individual plans but bills separately on usage. It isn’t part of the base subscription price, so factor it in if you plan to run it on every pull request.
There’s one plan the table above leaves out on purpose: Cursor Start, launched in July 2026 at ₹649/mo for developers in India. It covers Cursor’s own models and Cloud Agents but drops the Other Models pool, Bugbot, Auto, and on-demand usage, and it runs its Grok models at a fixed medium effort with no fast mode. We track USD pricing for a US/UK audience, so it stays out of the plan table and lives in the changelog instead.
Team pricing splits the same way most seat-based tools do, except Cursor makes the usage tier a seat choice rather than a plan choice. A Standard seat is $40/user/mo; a Premium seat is $120/user/mo and gets 5x the usage allowance of Standard. Both carry a line item that’s easy to miss: on Teams and Enterprise, every third-party model request adds a Cursor Token Rate of $0.25 per million tokens on top of the model’s API price, whether that usage is included, on-demand, or on your own key. Cursor’s own models are exempt. Both seat types share the same collaboration features — centralized billing, usage analytics, team-wide privacy mode, SAML/OIDC SSO — so the only reason to pay for Premium seats is genuinely heavy per-user agent usage, not access to a locked feature. Enterprise drops the per-seat menu in favor of custom pricing, pooled usage across the org, SCIM provisioning, audit logs, and invoice billing: the stuff procurement teams ask for that self-serve billing can’t do.
So which tier actually fits? If you’re mostly using Tab completions and light Agent work, Pro’s Other Models pool rarely gets touched, since Tab doesn’t count against it and Cursor’s own models draw from their separate included pool — Cursor’s docs put both daily Tab users and limited Agent users inside the included allowance. If you run agentic workflows daily and like picking your model by hand, budget for Pro Plus or Ultra rather than assuming Pro will cover it. Cursor’s own docs estimate daily Agent users at typically $60–$100/mo in total usage, which lines up almost exactly with the Pro Plus tier. Power users running multiple parallel agents or heavy automation should expect Ultra-level spend regardless of which sticker-price plan they’re nominally on. The number on the pricing page was never the ceiling, and now it isn’t even a balance you can read.