Cursor for teams: what the Teams plan costs and includes

Cursor's Teams plan costs $40 a user a month, or $32 billed annually, for a standard seat, and $120 ($96 annually) for a Premium seat with five times the usage. Each paid seat gets its own monthly usage in two pools, one for Cursor's own models and one for other companies' models; usage doesn't pool or transfer between teammates, and beyond it Cursor bills on-demand usage, which is on by default. Teams adds central billing, an admin dashboard, usage analytics, org-wide privacy mode, single sign-on and shared team rules. Enterprise, at custom prices, adds pooled usage, SCIM, audit logs and per-member spend limits.

Key takeaways

• Seats: Standard $40 a month ($32 annually), Premium $120 ($96) with five times the usage, and free admin-only seats. You can mix them.
• Usage: per user, in two pools, reset every billing cycle. Cursor doesn't publish the dollar size of either pool.
• Overage: on by default. Third-party models cost their API price plus $0.25 per million tokens; Cursor's own Composer and Grok models skip that fee.
• Spend limits on Teams are team-wide only. When the team hits its limit, everyone using on-demand usage loses AI features until it resets.
• Coming change: OpenAI plans to stop supplying its models to Cursor, with a proposed transition period running to November 12, 2026.

How much does Cursor cost for a team?

• Standard seat: $40 a user a month, $32 billed annually.
• Premium seat: $120 a month, $96 annually, with five times a standard seat's usage, introduced on June 1, 2026 (Cursor).
• Unpaid admin seat: free, for people who manage the team without using the product.

Annual billing saves 20%. Cursor publishes no maximum team size or Teams trial; larger teams negotiate Enterprise.

How do Cursor Teams usage limits work?

Each paid seat gets two monthly pools (Cursor):

• Cursor models: Composer 2.5 and the Grok models, which Cursor now counts as its own since SpaceX bought it.
• Other models: Claude, GPT and the rest, at their API prices.

Usage "is allocated per user based on seat type, does not transfer between team members," and resets each cycle. When someone uses up the third-party pool, Cursor moves them to its own models; beyond both, on-demand usage takes over, with third-party models charged their API price plus Cursor's $0.25-per-million-token rate. Cursor hasn't published the dollar value of either pool.

Spend limits: Teams can set one monthly limit for the whole team, which can scale with seat count. When it's reached, everyone on on-demand usage loses AI features (Cursor). Per-member limits need Enterprise.

What does Teams add over Pro?

• Central billing and an admin dashboard with member and admin roles.
• Usage analytics with CSV export.
• Privacy mode enforced for the whole organization.
• SAML or OIDC single sign-on at no extra cost.
• Team rules, either enforced or optional, and a team marketplace for skills, plugins and MCP servers.
• Shared transcripts: read-only links that teammates can fork into their own Cursor.
• An admin API and a data processing agreement.

Enterprise only: SCIM, audit logs, service accounts, pooled usage, per-member spend limits, model and MCP restrictions, repository blocklists, customer-managed keys and invoicing (Cursor).

How do teams collaborate in Cursor?

• Cloud agents are visible to teammates with access to the repository, read-only. An admin setting called Team follow-ups lets teammates message someone else's cloud agent; Cursor's docs warn that the agent runs with its creator's secrets (Cursor).
• Slack: @Cursor starts a cloud agent that reads the whole thread.
• Linear and GitHub: assign an issue or mention @Cursor.
• Bugbot reviews pull requests; since June 2026 it bills per run, about $1 to $1.50, from the team's on-demand spend (AI code review tools).

What Cursor doesn't have is two people steering one agent live. Cursor staff wrote in July 2026 that local agent sessions don't sync between people in real time. More in Poly vs Cursor.

What is changing for Cursor teams?

• SpaceX completed its $60 billion purchase of Cursor on August 14, 2026. Seat prices didn't change; xAI's Grok models moved into Cursor's own pool.
• OpenAI says it plans to wind down its contract supplying models to Cursor, with a proposed transition period to November 12, 2026, and no confirmed end date yet. Its suggested workarounds are your own OpenAI API key in local Chat and Agent, or the Codex extension inside Cursor. Your own key doesn't work for Tab, Auto, cloud agents or the CLI (OpenAI).
• Auto mode now bills at the routed model's list price, since Cursor's router launched in July 2026.

How does it compare with Claude and Copilot?

• Claude Team: $20 a seat billed annually or $25 monthly, premium seats $100 or $125, 2 to 150 seats, with Claude Code included (Claude Code for teams).
• GitHub Copilot: Business $19 and Enterprise $39 a user, with AI credits pooled across the organization (Claude Code vs GitHub Copilot).

Cursor is the priciest standard seat of the three, and the only one of them built as a full editor.

A team working with one agent

Cursor's team features share the work after it happens: transcripts, cloud agents others can view, rules everyone inherits. Poly (usepoly.co) is built for the session itself: a browser room where a team works with one coding agent, Claude Code or Codex, sees each step live, and any member can approve or undo a change. Free to start. What is Poly?