Cursor Usage Limits (2026): Why Every Tier Is a Multiple of a Number Cursor Never Publishes

The short answer

Cursor publishes a price ladder and no limits. As of September 20, 2026, cursor.com/pricing lists Hobby free with "Limited Agent requests", Pro at $20 a month with "Extended limits on Agent", Pro+ at $60 with "3x Pro limits on Agent", Ultra at $200 with "20x Pro limits on Agent", and Teams at $40 per user with pooled usage. Nowhere on the page is there a request count, a token count or a window length. Every tier is a multiple of Pro, and Pro is a multiple of nothing you can see.

That sounds like a dead end, and mostly it is. But the multipliers plus the prices do support exactly one piece of arithmetic, and it changes which tier you should buy.

What Cursor actually publishes

Here is the ladder, quoted from the plan cards and the page's own structured data, read today:

Yearly billing takes 20% off every paid tier. Bugbot, the code reviewer, is listed as "on usage-based billing" on Pro, Pro+ and Ultra alike, which means it is metered outside whatever your agent allowance is.

I went looking for the numbers in the documentation too. As of today, docs.cursor.com/en/account/pricing returns a JavaScript application shell to a plain fetch, with no limits table in the served HTML. That is a note about what is machine-readable, not an accusation: it does mean that anything you read about Cursor's limits on a third-party page was either taken from a screenshot or carried over from the retired 2025 "fast requests" plans, which is why the numbers in those posts disagree with each other.

The math the pricing page does not do for you

Call Pro's unpublished agent allowance one unit. It does not matter what a unit is — a request, a token, an hour of agent time — because the multipliers are stated relative to it, so the unknown cancels.

• Pro: $20 for 1 unit. $20 per unit.
• Pro+: $60 for 3 units. $20 per unit.
• Ultra: $200 for 20 units. $10 per unit.

Pro+ is priced exactly in line with Pro. Three times the money for three times the work is not a discount, it is a bigger tank at the same price per gallon. The only reason to buy it is that you need the headroom inside one seat and cannot split the work across two Pro seats, which for a solo developer is a real reason and for a two-person team usually is not.

Ultra is the only tier on the ladder that changes the unit economics: it halves the cost of each unit of agent work. That reframes the decision. The question is not "is Ultra worth $200", it is "do I use more than ten Pro plans' worth of agent time", because at exactly ten units Ultra and Pro cost the same and above it Ultra is cheaper per unit while still giving you double the headroom.

The same logic applies sideways to Teams at $40 a user. You pay double Pro per person, and what you get back is pooling. If your team's usage is even, pooling is worth little and Teams is a 100% premium for invoicing and admin. If it is lumpy, which in my experience it always is, pooling is the whole product.

What this costs you in practice

Because the base is unpublished, you cannot size a plan before you buy one, and no article can size it for you. What you can do is treat the first month as measurement: start on the tier you think is right, watch the in-product usage display rather than the pricing page, and move once you have a month of your own numbers. That is a worse experience than reading a table, and it is the actual state of the tool as of September 2026.

Two things reliably distort that first month, and both are worth removing before you judge a tier. The first is leaving the agent on a frontier model for work that does not need one, which burns allowance faster than any other habit. The second is treating the agent like a chat window — long, wandering threads cost more than several short scoped ones, because each turn carries the accumulated context with it.

For what the tiers cost rather than what they allow, including how the metering shows up on a bill, I keep a separate breakdown in Cursor pricing. If you are choosing between tools rather than tiers, Cursor vs Claude Code vs Codex is the three-way comparison, and it covers what each one does when you hit the wall mid-task.

How this compares to the rest of the category

Cursor is not an outlier any more. Anthropic stopped publishing a message count for Claude Code and now describes allowances the same relative way — Pro is "at least 5x" Free, Max is "5x or 20x" Pro — with one pool shared across chat, desktop and the terminal; I wrote that up in Claude Code usage limits. The difference is that Anthropic at least publishes the window the allowance resets on. Cursor publishes neither the size nor the window.

The practical effect across the category is the same: limits have moved from a number you can plan against to a feeling you discover. If you are trying to budget an AI stack across several of these tools at once, the side-by-side of where the caps land on ChatGPT, Claude, Gemini and Copilot is in AI usage limits, which I re-check every Monday for exactly this reason.

Which tier should you actually buy?

If you are trying Cursor, Hobby is a trial of the editor, not a free tier for agent work — frontier models, cloud agents and MCPs all sit behind Pro. If you code with it most days, Pro at $20 is the right starting point and the only honest recommendation anyone can make, because nobody outside Cursor can tell you whether that allowance fits your week. If you hit the ceiling weekly, skip Pro+ unless you specifically need headroom in one seat, since it costs the same per unit as Pro. If you are living in the agent all day, Ultra is where the price per unit halves, and it is the only upgrade on this ladder that is cheaper rather than simply bigger.

If the reason you are burning through agent limits is that an AI-built codebase keeps breaking and you keep asking the agent to patch it, the limit is not your problem. That is what Vibe Code Rescue is for: a fixed-scope rebuild of the parts that are costing you a re-prompt a day.