Skip to lesson
Exit
Cursor Product & Architecture1 / 3

1 min lesson

Accounts, billing & enterprise

Describe what "A large share of 'Cursor is broken' tickets never touch the editor" changes in practice.

Step 1 of 3

A large share of "Cursor is broken" tickets never touch the editor. They're billing confusion, an SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition. misconfig or a corporate proxy quietly dropping requests.

These are the tickets an admin escalates loudly, so they're where a support engineer earns enterprise trust. Config questions go to docs and the admin; real defects go to Engineering.

Learn more

Advanced table

Plans, usage and the billing tickets that aren't bugs

Plans, usage and the billing tickets that aren't bugs

Plan
Free, $0
Roughly who it's for
Trying it out
Why behavior differs
Limited usage and no third-party models
Plan
Plus, $8
Roughly who it's for
Light, introductory use
Why behavior differs
Cursor models only, namely Grok 4.7Cursor and SpaceXAI's current lead Cursor model, in the weekly pool at $2 per million input tokens and $6 per million output, with a 256k context window and a 500k variant; above 256k input tokens it bills at 2x the standard rate. Press Enter for the full definition., 4.6, 4.5 and Composer 2.5The current Composer release, better at long-running tasks and at judging when a job needs a light touch versus deep work. Press Enter for the full definition., at fixed settings; no Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition., BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition., Origin, Auto or third-party models
Plan
Premium, $30
Roughly who it's for
New Agent users
Why behavior differs
4x Plus usage; adds Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition. and Automations, Origin, BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. and third-party models at API list price from prepaid credit
Plan
Super, $100 and Ultra, $200
Roughly who it's for
Daily Agent users and power users
Why behavior differs
15x and 50x Plus usage
Plan
Teams
Roughly who it's for
Small-to-mid teams
Why behavior differs
Premium, Super or Ultra seats at $30, $100 and $200, with Plus not offered; centralized billing and SAMLSecurity Assertion Markup Language. The XML-era enterprise standard that powers single sign-on: your identity provider vouches for you to each app. Older than OIDC but still what many enterprise tools speak. Press Enter for the full definition./OIDCOpenID Connect. The modern single sign-on standard, built as an identity layer on top of OAuth 2.0. Where SAML is XML and enterprise-legacy, OIDC is JSON and what newer tools implement first. Press Enter for the full definition. SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition.
Plan
Enterprise
Roughly who it's for
Large orgs with security needs
Why behavior differs
Custom pricing, pooled usage, SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition., admin controls and audit logs

When two users see different behavior, the plan is often the whole story. Hobby, Start, Pro $20, Pro+ $60, Teams Standard $40 and Teams Premium $120 are legacy plans still honoured for existing customers, so an older account can show the older billing model.

Most billing tickets are usage or pricing confusion rather than defects, and the rows below map the common complaints to their real cause.

Billing tickets, decoded
"It stopped working mid-task"
Often the weekly pool is used up, not an outage. It refreshes weekly, and top-ups or the monthly additional usage limit decide whether work continues. Check plan and usage.
"My bill is higher than expected"
Third-party models bill at API list price from prepaid credit. Teams and Enterprise also add the $0.25 per million token Cursor Token Rate on that usage; individual plans don't pay it.
"Claude, GPT or Gemini is missing or billed separately"
No plan's pool includes third-party models. Plus has none, and Premium and above buy them at API list price.
"A teammate has features I don't"
Different plan or seat assignment. Check seat management and plan.
"I upgraded but nothing changed"
Sign-out and sign-in to refresh entitlements, then confirm the seat applied to the right account.

Route these to clear explanation and docs, not to Engineering. New plans bill at grok.com/dashboard/billing and legacy plans at cursor.com/dashboard/billing.

Learn more

Optional practice

Test yourself on Accounts, billing & enterprise

QA Plus subscriber asks why Claude is not in their model picker while a teammate on a Premium seat has it. What do you tell them?