Pricing

Cursor Teams gains two usage pools and a $96 seat

The June restructure separates first-party from third-party spend and adds a $96 seat. The interesting detail is what Cursor has not published about included usage.

What happened: 1 June 2026 · Written: 31 August 2026
Announced 1 June 2026; applied to renewing customers from 1 July.

The short answer

Cursor split every Teams seat into two included-usage pools, first-party and third-party, and added a Premium seat at $96 per seat per month annually, $120 monthly, alongside the unchanged Standard at $32 and $40. It applied to new customers immediately and renewals from 1 July 2026. Measure usage before buying Premium seats.

Annual and monthly are different billing terms for the same unit; both are shown.

What changed on 1 June

Cursor published the change on 1 June 2026. Every Teams seat now comes with two separate pools of included usage: a first-party pool, which the announcement described as covering Auto and Composer 2.5, and a third-party API pool consumed by outside models. The split is the structural part of the news. Spending on an external model no longer eats the allowance your team relies on for everyday work inside Cursor’s own tooling.

The Standard seat keeps its price and gains more included usage: $32 per seat per month on annual plans, $40 on monthly. Above it sits a new Premium seat at $96 per seat per month annually, or $120 monthly. Cursor’s own framing is five times the included usage of a Standard seat at three times the cost. Teams can mix the two seat types freely, so nobody has to move the whole company at once.

Timing matters for budgeting. The new structure applied immediately to new customers, and from 1 July 2026 to renewing ones, which means most existing teams passed through the change at their renewal date rather than on announcement day. If your renewal has already come and gone, you are on the two-pool model now, whether or not anyone in the finance chain noticed the seat definitions had changed underneath them.

The maths of the Premium seat

On paper the Premium seat is the better rate: five times the included usage for three times the price, by Cursor’s own accounting. That holds only for a developer who actually consumes the larger allowance. Bought for someone who does not, the gap between $32 and $96 per seat per month buys headroom nobody touches, and a cheaper per-unit rate becomes an expensive way to describe capacity you never used.

The figure Cursor does not put in the announcement is what included usage amounts to in absolute terms. The multipliers are relative: Premium against Standard, not usage against any published unit. Without that, no team can model the Premium seat from the pricing page alone. You can only work it out backwards, from what your own heaviest users were already spending before the change, which is a measurement job rather than a purchasing decision.

Cursor did ship the instrument for that job alongside the pricing. Admins get real-time usage visibility and can configure alerts on dollar thresholds, delivered through Slack or email. It is a sensible addition, and worth reading for what it implies: a pricing model with two pools and two seat tiers needs monitoring to be usable at all. The tooling is not a bonus here so much as a prerequisite for the structure it accompanies.

What the docs say that the blog did not

Three months on, the documentation does not match the announcement word for word. The June post described the first-party pool as Auto and Composer 2.5. The current pricing docs describe each paid seat as carrying included usage across two pools, with the Cursor models pool listed as Cursor Grok 4.6, Grok 4.5 and Composer 2.5. The list has moved since June, which is the ordinary consequence of tying a pricing tier to named models.

That is the part to watch rather than the headline prices. Which pool a model sits in decides whether using it draws on the generous included allowance or the third-party one, and Cursor controls that assignment. A model your team standardised on because it was first-party is not contractually fixed there by anything in the announcement. The prices are stable and published; the boundary that makes them meaningful is neither.

One smaller discrepancy is worth noting before you quote a figure internally. The current docs list only the monthly rates, $40 per user per month for Standard and $120 for Premium with five times the usage. The annual rates of $32 and $96 come from the June announcement. Both are Cursor’s own published numbers, but if you are building a budget from the docs page alone you will be working from the higher of the two.

How to work out your own seat mix

Start by measuring rather than deciding. The freedom to mix seat types means the default position is Standard for everyone, with Premium bought only for the people whose measured consumption justifies it. Run the new admin usage view across a full billing cycle first, rank your developers by what they actually draw down, and treat the ranking as the input. Anything else is guessing at a five-to-three ratio you cannot verify.

Then set the alerts and keep the two pools apart in your reporting, because a third-party overage and a first-party one are now different problems with different fixes. Before you standardise the team on any model, check which pool the docs currently place it in, and check again at renewal. The seat prices will probably hold. The composition of the pool behind them has already changed once since June.

What to do about it

Do not buy Premium seats on the ratio alone. Enable the admin usage view, watch a full billing cycle, and rank developers by actual consumption before upgrading anyone. Keep everyone on Standard by default, set dollar-threshold alerts in Slack or email, and re-check which models sit in the first-party pool at every renewal.

Read our Cursor review →

Questions readers ask

How much does a Cursor Premium seat cost?

$96 per seat per month on annual plans and $120 per seat per month on monthly plans. Cursor states it carries five times the included usage of a Standard seat at three times the cost. The Standard seat stays at $32 annual and $40 monthly.

When does the new Cursor Teams pricing take effect?

It applied immediately to new customers from the 1 June 2026 announcement, and from 1 July 2026 for renewing customers. Existing teams therefore moved onto the two-pool structure at their own renewal date rather than all at once.

Can a team mix Standard and Premium seats?

Yes. Cursor says teams can mix seat types freely, and the current docs describe seat type as independent of a user’s role. That makes Standard the sensible default, with Premium reserved for the people whose measured usage justifies it.

Where every figure came from

Each claim above was checked against a primary source, then checked again by a second reader who had not seen the first check. Open any of them and verify us.

Each paid Cursor Teams seat now carries two separate usage pools: one for first-party models (Auto and Composer 2.5) and one for third-party APIs. cursor.com 2026-06-01
The Standard seat keeps its price and gains more included usage: $32 per seat per month billed annually, $40 billed monthly. cursor.com 2026-06-01
Cursor introduced a new Premium seat at $96 per seat per month billed annually, and $120 billed monthly. cursor.com 2026-06-01
The Premium seat carries five times the included usage of a Standard seat for three times the price. cursor.com 2026-06-01
A team can mix Standard and Premium seats freely. cursor.com 2026-06-01
The change applied immediately to new customers, and from 1 July 2026 to renewing ones. cursor.com 2026-06-01
The announcement was published on 1 June 2026. cursor.com 2026-06-01
Current documentation confirms the monthly price of both seat types and states that seat type is independent of a member’s role. cursor.com 2026-09-01
Documentation describes the two included usage pools on every paid seat, with the first-party pool now covering Cursor Grok 4.6 and Grok 4.5. cursor.com 2026-09-01
Admins gained real-time usage tracking and dollar-threshold alerts delivered over Slack or email. cursor.com 2026-06-01