Cursor’s plans and their pricing
All individual plans include:
There are three individual plans:
Individual limits are computed using agent API prices and will always be greater than the cost of one’s plan. For example, Pro includes over $20 of agent model inference at API prices per month.
Expected usage within limits for the median user per month:
Models like Opus 4 consume more tokens per request and reach usage limits faster than other models. We recommend selectively and intentionally choosing these models.
Each plan includes a monthly agent usage budget computed at API prices. For example, Pro includes at least $20 of usage per month. Each agent message deducts from this budget based on the model’s API pricing.
You can view all requests and token breakdowns on your dashboard.
Once monthly usage limits are exhausted, you will be notified explicitly and shown a message with three options:
Requests are never downgraded in quality or speed. Explicit error messages are always shown when users hit usage limits.
All teams plans include:
Cursor bills per active user, not seats. Add or remove users anytime and billing will adjust immediately.
Refunds appear as account credit on your next invoice. Your renewal date stays the same.
Team limits are computed by request. Each teams seat comes with 500 included agent requests per user per month. Each time you use an agent, most models will spend one request. A few will cost more:
If you’d prefer, you can purchase additional requests for $0.04 each.
There are two teams plans: Teams ($40 / mo) and Enterprise (Custom). We recommend Teams to any customer that is happy self-serving. We recommend Enterprise to large customers that need priority support / account management, order forms, annual invoicing, or SCIM.
The limits included in individual and teams subscriptions are sufficient for most users. If you do reach your limits for an agent model, you can purchase additional usage at API rates (for individuals) or request-based pricing (for teams).
Certain models have the ability to use Max Mode, which allows for longer reasoning and larger context windows. While the majority of coding tasks do not need to use Max Mode, it can be helpful for more complex queries, especially with large files or codebases. Using Max Mode will consume more usage. You can view all requests and token breakdowns on your dashboard.
BugBot is included for free in all plans during our preview period.
Background Agents are charged at API pricing for the selected model. You’ll be asked to set a spend limit for Background Agents when you first start using them.
Virtual Machine (VM) compute for background agents will be priced in the future.