This article was originally published on aicoderscope.com
TL;DR: Standard keeps its $40/month price but ships with substantially more included usage; a new Premium tier at $96/seat/month annual gives 5× that for 3× the price. Usage is now split into two separate pools — Cursor-native and third-party API — so billing surprises finally have a source. For most teams, assigning Premium to your 2–3 heaviest users and Standard to everyone else cuts the monthly bill nearly in half versus going all-Premium.
| Standard | Premium | Windsurf Teams | |
|---|---|---|---|
| Best for | Regular coders, light-to-moderate agent use | Daily Claude Opus, overnight agent runs | Teams wanting flat-rate simplicity |
| Monthly price | $40/seat | $120/seat | $40/seat |
| Annual price | $32/seat | $96/seat | — |
| Usage vs. Standard | 1× baseline | 5× | Quota-based, not pooled |
| The catch | Third-party pool runs dry faster than Composer pool | $96/seat stings if usage is only moderate | No per-user seat type mixing |
Honest take: On a 10-person team, put the 2 engineers who run agents all day on Premium and everyone else on Standard. Monthly cost drops to roughly $450 instead of $960 for all-Premium — and the other 8 developers won't notice the difference.
What broke before and why this update exists
The August 2025 Teams pricing update moved agent usage from fixed request caps to variable token-rate billing. That change made economic sense — a 20-file refactoring run consumes far more compute than a single file rename, and flat request counts never reflected that. But the rollout came with one critical flaw: the usage meter was a single opaque number showing percentage-to-limit, with no breakdown of what was driving the charge.
Teams that defaulted to Claude Opus or GPT-4o for routine Composer sessions discovered their third-party API spend was 80% of their bill only after the invoice landed. Community forum threads filled up. The recurring complaint was not that Cursor was expensive — it was that Cursor was unpredictably expensive.
The June 2026 update has three practical goals: give Standard seats more included usage at the same price, create a Premium tier that actually serves power users without penalizing everyone else, and split the usage meter so admins can see the bill before it arrives.
The two usage pools, explained
Every Teams seat now carries two separate meters:
Pool 1 — Composer and Auto: Tracks consumption against Cursor's first-party models and the Auto agent feature. This is where most developers spend the majority of their usage — code completions, Composer sessions, and agent tasks running on Cursor's own inference stack. Cursor claims the Composer pool on a Premium seat covers a full month of heavy agent use for 99% of users.
Pool 2 — Third-Party API: Tracks usage of external models routed through Cursor: Claude Sonnet, Claude Opus, GPT-4o, Gemini Pro, and similar frontier models. This is where bills balloon for teams that set a frontier model as their default and never reconsider it.
The operational implication: a developer who uses Cursor's native models heavily will almost never hit Pool 1. A developer who routes every Composer request through Claude Opus will drain Pool 2 independent of which seat type they have — the only difference is how large that bucket is before overages begin.
Neither seat type offers unlimited third-party API calls. Both pools have limits; Premium's are 5× larger. If your entire team treats Claude Opus like autocomplete, the correct answer might be billing Anthropic directly via the API and setting a spending cap there, not buying Premium seats.
Standard at $32/seat (annual): who it actually serves
Standard costs $32/seat/month on an annual commitment or $40/seat/month month-to-month — identical monthly price to the pre-June plan, but with substantially more included usage in both pools.
What Standard covers:
- Full Cursor IDE with all features (Cursor Tab, Composer, Auto, BugBot)
- Significantly expanded Composer/Auto pool vs. pre-June baseline
- Third-party API pool for Claude and GPT usage (larger than before, but still finite)
- Centralized team billing, usage dashboard, spend alerts
- SSO (SAML/OIDC), RBAC, org-wide privacy mode
Standard handles the typical developer workflow: Cursor Tab completions running continuously, a few Composer sessions per day, occasional Auto agent runs for focused tasks, some Claude or GPT usage for complex reasoning. The pool expansion resolves the "hit the cap in week two" problem that plagued the August 2025 rollout for normal usage patterns.
Standard breaks down when a developer routes every session through a frontier model, runs Auto as an all-day background process, or regularly kicks off multi-file agent tasks that span hundreds of API calls. One or two developers on every mid-size engineering team fit this profile. The new Premium tier exists specifically for them.
Premium at $96/seat (annual): when the arithmetic holds
Premium delivers 5× the combined pool size of Standard at 3× the price. Per usage-unit, it's cheaper than Standard-plus-overages for heavy consumers.
The break-even math: at the $64 annual-rate price gap between Premium ($96) and Standard ($32), overage charges need to exceed $64/month before Premium pencils out. At typical third-party API token rates, $64 in Claude Opus overages represents roughly 450K–700K output tokens beyond the Standard pool — achievable in a month of intensive agent development but not a baseline for most engineers. Developers who run overnight automated coding agents, who use Claude Opus for every Composer request across a full workday, or who regularly run cross-repository refactoring tasks are in this category.
Premium is not an "unlimited" plan. Both pools have ceilings, just 5× higher than Standard. Cursor's own framing is that Premium covers "99% of heavy agent users" for a full month — which also implies the 1% who exceed it will still see overages.
What Premium is not the answer for: a developer who occasionally runs a long agent task but mostly uses Cursor Tab and standard Composer. That profile pays $64/month extra for headroom they rarely touch.
Mix-and-match: the structural change that actually matters
The June 2026 update lets Teams admins assign Standard or Premium seats per user. Previous Cursor Teams plans required the same tier for everyone. This is the change that makes the pricing math work for real teams.
A realistic breakdown for a 10-person team:
| Seat count | Profile | Seat type | Annual rate |
|---|---|---|---|
| 2 | Senior engineers, daily agent runs, Claude Opus heavy use | Premium | $96/month |
| 5 | Mid-level engineers, daily Cursor Tab + regular Composer | Standard | $32/month |
| 3 | Junior / occasional Cursor use, mostly completions | Standard | $32/month |
Monthly bill on annual plan: (2 × $96) + (8 × $32) = $448/month
All-Premium alternative: 10 × $96 = $960/month
All-Standard with overages for the two power users: $320 base + estimated $100–$200 in monthly third-party API overages = $420–$520/month — roughly equivalent to the mix-and-match approach but less predictable.
The mix-and-match approach delivers predictability without the overhead cost of blanket Premium. For a 20-person team with 4 heavy users, the savings scale proportionally: (4 × $96) + (16 × $32) = $896/month vs. $1,920 all-Premium.
The usage dashboard now shows per-user consumption broken down by pool, so admins can identify who is approaching limits and reassign seat types at the next billing cycle. Cursor also says it will surface recommendations when a user's behavior consistently indicates they'd benefit from a seat upgrade — useful if accurate, a vendor upsell nudge if not.
The rebuilt spend-alerting system
The June update overhauled spend alerts. Admins can now configure dollar-based thresholds and receive notifications via Slack or email. The previous system showed a percentage bar that gave no signal abo
Top comments (0)