Cursor pricing in 2026: plans, usage limits, and what to do when it gets too expensive
Published October 9, 2026
Summary
Cursor’s individual plans run from free to $200 a month, and Teams seats cost $40 or $120. The plan price is only the starting point: agent work draws from usage pools billed at API rates, and on-demand usage keeps going after the pools run out. This guide covers every plan, why Cursor bills climb, how to lower them, and cheaper ways to run the same coding agents. Checked against Cursor’s pricing page and documentation on October 9, 2026.
At a glance
Cursor plans and prices
Paid individual plans share the same features: unlimited Tab completions, extended agent limits on every model, Bugbot, and Cloud Agents. What changes from Pro to Ultra is how much model usage is included. Teams and Enterprise add team billing, administration, SSO, and usage controls.
| Plan | Price | Included usage | When it runs out |
|---|---|---|---|
| Hobby | Free, no credit card | Limited agent requests and access to Composer | Upgrade to a paid plan |
| Pro | $20/month | Two monthly pools: Cursor’s own models, and third-party models at API prices | On-demand usage at the same API rates, billed after the month ends |
| Pro+ | $60/month | Larger pools; Cursor recommends it for daily agent users | Same as Pro |
| Ultra | $200/month | Largest individual pools; Cursor recommends it for agent power users | Same as Pro |
| Teams Standard | $40/user/month, or $32 billed annually | A per-seat allowance in both pools that is not shared across the team | On-demand usage, on by default, plus a $0.25 per million token rate on third-party models |
| Teams Premium | $120/user/month, or $96 billed annually | 5× the usage of a Standard seat | Same as Teams Standard |
| Enterprise | Custom | Usage pooled across the team, with invoicing and SCIM | Set by contract, with per-member spend limits |
How the two usage pools work
The Cursor Models pool covers Cursor’s own models, Grok 4.7, Grok 4.6, Grok 4.5, and Composer 2.5, and includes “significantly more” usage than the second pool. The Other Models pool covers Anthropic, Google, and other third-party models, charged at each model’s API price. Cursor doesn’t publish how many dollars or tokens either pool holds, and it notes that “your model selection affects how quickly your included usage is consumed.”
On Teams, when a member uses up the third-party pool, Cursor moves them to the Cursor Models pool. If they keep choosing third-party models, or use up both pools, they continue on on-demand usage. Developers in India can also choose Start at ₹649 a month, which covers only Cursor’s own models.
Real monthly cost
What Cursor actually costs each month
Cursor publishes its own estimate of total monthly usage. People who mostly use Tab completions, or use the agent occasionally, usually stay within the included usage of Pro. People who use the agent every day typically spend $60 to $100 a month in total. Power users running several agents or automations often spend more than $200.
What decides where you land is the model. Every agent turn rereads the conversation and the files it touched, so long sessions on frontier models use the most. These are Cursor’s published rates per million tokens:
| Model | Pool | Input | Output |
|---|---|---|---|
| Composer 2.5 | Cursor Models | $0.50 | $2.50 |
| Grok 4.7 | Cursor Models | $2 | $6 |
| Composer 2.5 (Fast) | Cursor Models | $3 | $15 |
| Claude Sonnet 5.5 | Other Models | $2 | $10 |
| Gemini 3.1 Pro | Other Models | $2 | $12 |
| Claude Opus 5.5 | Other Models | $4 | $20 |
| Claude Fable 5.1 | Other Models | $10 | $50 |
Why bills climb
Why Cursor gets expensive
Most complaints that Cursor is too expensive come from the same few mechanics. None of them are hidden, but together they mean the plan price says little about the final bill.
- The plan price is a floor. Once the included pools are used up, on-demand usage continues at the same API rates and is billed after the month ends. Cursor never slows or downgrades requests, so nothing tells you to stop.
- Frontier models use up the pools fastest. Claude Opus 5.5 output costs 8× as much as Composer 2.5, and Claude Fable 5.1 costs 20× as much. Fast modes cost more again: Composer 2.5 Fast is 6× the standard rate, and Grok 4.7 doubles its rate past 256K tokens of context.
- Teams spending is hard to cap per person. On-demand usage is on by default, each seat’s allowance can’t be shared with teammates who use less, and only Enterprise can set a spend limit for each member.
- Teams and Enterprise pay a Cursor Token Rate of $0.25 per million tokens on every third-party model request, including when Auto picks the model and when you bring your own API key.
- Background work adds up quietly. Cloud Agents bill model usage at API rates, and Bugbot on individual plans is billed by usage.
- A few people drive most of the bill. Cursor said so itself when it changed Teams pricing in June 2026: “a small number of power users on any team tend to drive the majority of spend.”
Cost control
How to lower your Cursor bill
If you want to stay on Cursor, these changes make the biggest difference, roughly in order.
- Use Composer 2.5, or Auto in Cost mode, for routine edits, and save Opus and Fable for problems that need them.
- Leave Fast mode off unless you are waiting on the result.
- Start a new chat for each task instead of extending one long session, so each turn rereads less context.
- On Teams, set a monthly team-wide spending limit, and check the usage dashboard for each pool every week.
- Move your heaviest users to Premium seats. They cost 3× a Standard seat for 5× the usage, and Cursor expects Premium’s first-party pool to cover a full month of heavy agent use for 99% of users.
- Pay annually on Teams: $32 instead of $40 for Standard, and $96 instead of $120 for Premium.
Flat-rate agents
A cheaper way to run coding agents: flat-rate subscriptions in the cloud
The largest Cursor bills come from metered frontier-model usage. If your engineers mostly want Claude or GPT models for agent work, the model providers sell flat-rate subscriptions for exactly that. Claude Max and ChatGPT Pro cost $100 or $200 a month, and when you reach a limit it resets on a schedule rather than billing you more, unless you choose to buy extra usage.
Replicas, which publishes this guide, runs those agents in the cloud on the subscriptions you already have. Claude Code signs in with your Claude subscription, Codex with your ChatGPT subscription, and OpenCode and Pi with a $10-a-month OpenCode Go plan. Replicas doesn’t resell model usage. You pay Replicas for cloud workspaces and your provider for the model, so you choose the ceiling on agent spend.
| Setup | Monthly price | Usage |
|---|---|---|
| Cursor Pro, Pro+, or Ultra | $20, $60, or $200, plus on-demand usage | Included pools, then on-demand usage at API rates |
| Cursor Teams | $40 or $120 per seat, plus on-demand usage | Per-seat pools, then API rates plus $0.25 per million tokens on third-party models |
| Claude Code on Claude Max 5x | $100 | 5× the Pro allowance per session; resets every five hours, with a weekly limit |
| Claude Code on Claude Max 20x | $200 | 20× the Pro allowance per session; same resets and weekly limit |
| Codex on ChatGPT Pro | $100 or $200 | No five-hour limit; weekly limits may apply |
| OpenCode or Pi on OpenCode Go | $10 | Usage caps on open coding models |
| Replicas Developer | $50 plus your agent subscription | 150 manual workspace hours a month for one person; API and automation runs bill at $0.008 to $0.016 a workspace minute |
| Replicas Team | $200 per Full seat, or $0.016 a minute on Flex, plus your agent subscriptions | Unlimited manual workspace hours on Full seats; Flex seats pay only for minutes used; API and automation runs bill at $0.008 to $0.016 a workspace minute |
What you get in a Replicas workspace
Every task runs in its own Linux VM built from an environment your team defines once, with your dependencies, services, and a browser. Start work from the web, desktop, or iOS app, Slack, Linear, GitHub, GitLab, a schedule, or the API, then review the diff and pull request. Several tasks can run in parallel without sharing a laptop or a branch.
When a subscription reaches its usage limit, Replicas moves the chat along a fallback chain you set: another credential for the same agent, or a fork to a different agent with the conversation carried over. A team that would rather switch tools than pay per token can put Codex right after its Claude subscription, ahead of an Anthropic API key. Analytics show agent time by person, agent, model, and credential.
Keep Cursor where it fits
Replicas also runs Cursor’s agent with a Cursor API key, billed to that user’s Cursor plan. Teams can keep Cursor for editing and run delegated work on whichever agent and subscription costs least for the job.
Check each provider’s terms before using a personal subscription on a hosted platform. Anthropic’s legal and compliance page sets out how Claude subscription sign-in may be used. Use an API key for production pipelines.
Honest take
When Cursor is still the better deal
Cursor isn’t expensive for everyone. Stay on it if most of these are true.
- You mostly use Tab completions and occasional agent requests, which Cursor says usually fit inside Pro’s $20.
- You want the agent inside your editor while you type. Replicas is a cloud workspace for delegated tasks, not an editor.
- Cursor’s own models do the job. Composer 2.5 costs $0.50 per million input tokens and $2.50 per million output tokens, far less than frontier third-party models.
- Your team needs Cursor’s Enterprise controls, such as pooled usage and per-member spend limits.
FAQ
Cursor pricing questions
Getting started with Replicas
Run Claude Code and Codex in the cloud on your own subscriptions
Replicas includes a 14-day free trial with no credit card required. Connect a GitHub or GitLab repository, define the environment once, sign in Claude Code, Codex, OpenCode, or Cursor with the subscriptions or keys you already pay for, and start a task from the web, desktop, or iOS app, Slack, Linear, or a pull request comment. Each task runs in its own Linux VM and comes back as a pull request your team reviews.