Cursor Teams Standard vs Premium Seats: The June 2026 Pricing Breakdown

Cursor quietly restructured its Teams plan this month in a way that will change the invoice for most engineering teams starting July 1. The short version: there are now two seat types — Standard and Premium — and every seat comes with two separate usage pools that track first-party Cursor model usage separately from third-party API calls. If you're on annual billing, the change takes effect on your next renewal. If you signed up this month, it's already live.

This post walks through the exact numbers, what the two usage pools mean in practice, and a framework for deciding which seat type to assign to which engineer before your billing cycle flips.

What changed

The old Teams plan was a single tier with a shared usage pool. The complaint from heavy agent users was predictable: they burned through their allocation in the first two weeks, hit the soft throttle, and either upgraded the whole team or managed usage by hand.

Cursor's fix is a seat split rather than a usage add-on. Standard seats cover the vast majority of developers — inline completions, Chat, occasional Composer runs. Premium seats are sized for the engineers running Composer all day, chaining multi-file agent sessions, or routing heavy GPT-5.5 and Opus calls through third-party models.

The new pricing numbers

Both seat types are available on annual and monthly billing. The discount for annual commitment is 20% on Standard and 20% on Premium — consistent across tiers.

Seat type    Annual/seat/mo   Monthly/seat/mo   Usage vs Standard
─────────────────────────────────────────────────────────────────
Standard     $32              $40               1×  (baseline)
Premium      $96              $120              5×  usage included

Teams can mix seat types freely — you don't have to assign the same tier to every engineer. The admin dashboard lets you assign and reassign seats without a support ticket. The billing invoice breaks down by seat type so you can see exactly which tier is driving cost.

Two usage pools explained

This is the part most teams miss in the announcement. Both seat types now split their included usage into two separate pools that don't share a bucket:

1. Composer and Auto pool— usage consumed by first-party Cursor models. This covers Cursor Tab (inline completions), Auto mode, and Composer sessions that route through Cursor's own inference infrastructure. These models are optimized for the IDE and tend to be faster and cheaper per token than routing through an external API.
2. Third-Party API pool — usage consumed when you select GPT-5.5, Claude Sonnet 4.6, Gemini 3.1 Pro, or any other external model in Composer or Chat. Cursor proxies the call to the provider, and that consumption draws from this separate bucket.

The pools don't cross-subsidize. An engineer who maxes out their Third-Party API pool still has their full Composer and Auto allocation, and vice versa. This matters for teams that route most agent work through Claude or GPT — those engineers were silently cannibalizing their Composer allocation under the old model.

                   Standard seat    Premium seat
──────────────────────────────────────────────
Composer + Auto    Baseline         5× baseline
Third-Party API    Baseline         5× baseline

Pools are independent — exhausting one does not draw from the other.

Who actually needs Premium

Cursor's claim is that the Premium Composer pool covers a full month of heavy agent usage for 99% of users. Here's how to read that: the 1% edge case is an engineer running Cursor Composer as a continuous autonomous agent — long overnight sessions, large multi-file refactors, CI-integrated agent pipelines. For everyone else, Premium is sized generously enough to avoid any throttle.

Practically, split your team into three buckets:

Engineer profile                              Seat recommendation
──────────────────────────────────────────────────────────────────
Tab completions + occasional Chat             Standard
Regular Composer, 1–3 agent sessions/day      Standard
Daily Composer, frontier models (Claude/GPT)  Premium
Full-day agent pipelines, CI-integrated       Premium (+ monitor)
Managers / non-daily users                    Standard

The simplest signal from the old plan: if an engineer ever hit the soft throttle before the 15th of the month, they're a Premium candidate. Pull the usage export from the admin dashboard to see the actual numbers per seat over the last 60 days before deciding.

Admin controls and spend visibility

The most practically useful part of the June update is the new admin tooling, not the seat split. Three things that weren't there before:

1. Real-time usage dashboard — per-seat, per-pool consumption visible with a day lag. You can see which engineers are approaching their allocation before they hit the throttle.
2. Personalized seat-type recommendations— the admin panel now surfaces a recommendation for each seat based on the last 90 days of usage. It's not a mandatory assignment, but it cuts the right-sizing research from a day to a glance.
3. Spending alerts — configurable dollar thresholds that fire via Slack or email. Set them at 50%, 80%, and 100% of expected monthly spend. This is the control that should have existed before, especially for teams mixing Standard and Premium seats.

Right-sizing your team before July 1

If your billing cycle renews in July, you have roughly one week to make seat assignment changes before they affect the next invoice. The steps are straightforward:

1. Pull 60-day usage export from Settings → Billing → Usage Export
2. Identify engineers who hit the soft throttle at any point
3. Flag engineers averaging > 500 Composer turns/week as Premium candidates
4. Assign Premium seats via Settings → Team → Seat Management
5. Set Slack alert at 75% of projected monthly spend
6. Review again after the first Premium billing cycle (30 days)

Quick math:
  N_premium × $96 + N_standard × $32
  vs.
  (N_premium + N_standard) × $40  ← old single-tier monthly cost

Break-even: Premium pays for itself vs upgrading ~3 Standard seats.

One thing Cursor doesn't make explicit: you can change seat types mid-cycle and the charge is prorated. If an engineer ramps up agent usage mid-sprint, you can upgrade their seat without waiting for the next billing date.

Cursor skills to pair with this

Getting more out of a Premium seat means actually running Composer efficiently — not just having more allocation. A few skills from skills-hub.ai that are worth installing if you're moving engineers to Premium:

# Skills that justify Premium seat investment
npx @skills-hub-ai/cli install cursor-parallel        # fan-out multi-file work in parallel
npx @skills-hub-ai/cli install cursor-cloud-agent-workflow  # /in-cloud pipeline recipes
npx @skills-hub-ai/cli install cursor-seat-optimizer  # audit usage and right-size seats

The cursor-parallelskill in particular is the one that turns a Premium seat from “more headroom” into a real throughput multiplier. It structures Composer sessions to fan out parallel agents across independent modules — which is exactly the workflow that chews through Standard allocation fastest but also produces the most output per hour.

Browse the full Cursor skill catalog at /cursor-rules or filter to agent workflow skills at /browse?platform=CURSOR&category=productivity.

The pricing restructure is a genuine improvement for power users, but the seat assignment decision is now a real one that affects monthly cost. Pull your usage data, map engineers to seat types before July 1, and set spend alerts on day one. The tooling Cursor shipped alongside the pricing change makes this tractable — the admin recommendations alone cut the analysis from a spreadsheet to a 30-minute audit.