All fixes · Cursor · Quota & billing

Cursor Usage Limit and “Monthly Limit Reached”: How to Fix

You've hit your usage limit

For companies: one company account, with a key and a fixed monthly budget for every person and app. Create a company workspace → or talk to us

Cursor shows “You've hit your usage limit” when your plan's included usage is spent. On a team, “You're out of usage. Switch to Auto or Composer 2.5, or ask your admin to increase your limit to continue.” means the spend limit your team set for additional usage is reached too, and an admin raises it in the team's billing settings. Cursor shows “You've reached your monthly limit. Set a new on-demand limit to continue.” when on-demand usage is also off or at the spend limit you set; turn it on, or raise or remove that limit, in the dashboard's Spending tab, or wait for the reset. Included usage resets monthly on the older Pro, Pro+ and Ultra plans and weekly on the X Subscription plans launched October 12, 2026, and on-demand spend limits reset with the next billing cycle. Developers leaving Cursor over this usually move to an open agent (Cline, Kilo Code or OpenCode) on a flat monthly API: you pick the model yourself, and Standard Compute costs a fixed price from $19/month with no usage-based overage.

What does each Cursor usage limit message mean?

Each message names a different limit. “You've hit your usage limit” means the included usage for the model you picked is spent; “You've reached your monthly limit. Set a new on-demand limit to continue.” means paid usage is off or at its cap too, so requests stop until the reset or until you raise the limit. The toast about switching to Composer is not an error at all.

  • “You've hit your usage limit”: your plan's included usage is used up for the selected model. Cursor staff call the block expected once the pool is spent, even if the Plan & Usage counter shows a lower percentage (a known display issue). Wait for the reset (weekly on the X Subscription, monthly on legacy plans), pick a model that is still included, or turn on paid usage.
  • “Total usage limit reached” with “You've reached your monthly limit. Set a new on-demand limit to continue.”: included usage is spent and on-demand usage is off or at its spend limit. Access is blocked until the monthly reset; the Set new limit button turns on pay-as-you-go with its own cap. On Teams, a small reduced-speed Auto and Composer allowance can run first, and this message appears when that is used too.
  • “Switched to composer-2.5 after reaching API limit”: your premium-model allowance is spent, so Cursor sends the request to its own included Composer model to keep the session going. Select Auto or Composer to stop the toast, or turn on usage-based pricing for premium models.
  • “… is not currently enabled in the slow pool. Please select another model, or enable usage-based pricing to get more fast requests.”: from the older request-based plans, where fast requests were used up and that model had no slow queue. Switch to Auto or enable usage-based pricing.
  • The X Subscription: when the weekly pool is spent, you can keep working from prepaid credit, wait for the weekly reset or upgrade. Once the Monthly additional usage limit (grok.com/dashboard/billing) is reached, paid usage pauses until next month even if credit remains.

What your own API key covers in Cursor →

Is Cursor down, or is it your limit? →

“Ask your admin to increase your limit”: what can a Cursor team admin change?

The message means you have used your included usage and reached the spend limit your team set for additional usage. Paid usage stops for you, the rest of the team keeps working, and it resumes at the start of the next period or as soon as an admin raises your limit. Where the admin does that depends on the plan.

  • The X Subscription Teams: only admins change the team's monthly additional usage limit and Auto Top-up, under Additional usage credits at grok.com/dashboard/billing. Admins also set a default monthly limit per member and override it for one person on the Members page.
  • Legacy Teams and Enterprise: the Spending tab at cursor.com/dashboard/spending. With “Only Admins Can Edit Usage Settings” on, only admins change on-demand usage and the team limit; with it off, any member can. Member and group overrides are Enterprise features and always admin-only.
  • The team limit is the default for every member without an override, and when several limits apply Cursor uses the highest one. Changing the team limit leaves existing overrides as they are.
  • On legacy Teams, reaching the team-wide limit cuts off on-demand usage for every member using it. Enforcement isn't instant, so spend can briefly pass the limit.
  • Or give every developer their own key: on Standard Compute every person and app gets a fixed monthly budget that never overruns, you can set spending caps per key and for the whole company, and all keys sit under one company account.

Cursor pricing for a team →

An LLM API for your team, with a budget per member →

What causes it

  • Plans include an allowance of model usage (a weekly pool on the X Subscription plans, a monthly one on legacy plans); agent-mode sessions with big context burn through it fast.
  • Long compose/agent runs resend large context every step, so usage scales with context, not just messages.
  • Team seats share the same behaviour: heavy users exhaust their allowance mid-month.

How to fix it

  1. Turn on on-demand usage (the older prompt says “Please enable usage-based pricing”) to keep premium models past the allowance at API rates. If on-demand is already on, raise or remove your spend limit in the dashboard's Spending tab; changes apply immediately.
  2. Switch day-to-day work to Auto / included models and save frontier models for the hard steps.
  3. Trim context: smaller @-mentions, fewer open files, shorter sessions.
  4. Bring your own key: on paid plans (Premium and above on the new plans) Cursor supports overriding the OpenAI base URL, so you can point it at a fixed-budget OpenAI-compatible endpoint.

Running an agent? Agent mode is the usage killer: every tool call resends the workspace context. If you live in agent mode, an allowance-based plan will always run out before the month does.

Sources: Cursor docs: pricing and on-demand usage; Cursor help: spend limits; Cursor help: usage and limits; Cursor staff: “You've hit your usage limit” on a spent pool (Sep 2026); Cursor staff: what “Set a new on-demand limit to continue” means (Jul 2026); Cursor staff: “Total usage limit reached” on Teams (Sep 2026); Cursor staff: the switched-to-Composer toast (Jul 2026); Cursor forum: the slow-pool message

Compare APIs for Cursor

Keep working on a fixed monthly plan

Cursor's “Override OpenAI Base URL” setting accepts any OpenAI-compatible endpoint. Point it at Standard Compute (base URL https://api.stdcmpt.com/v1, model = standardcompute) and chat/agent requests bill against a fixed monthly budget from $19/month: requests stop when it is used up, with no overage. Tab completion stays on Cursor's models, and the override needs a paid Cursor plan. What a custom key does and doesn't cover in Cursor: /cursor-own-api-key.

Cursor settings
Override OpenAI Base URL  https://api.stdcmpt.com/v1
OpenAI API Key            YOUR_API_KEY
Model                     standardcompute

Plans from $19 a month with $19 of compute. Eligible new accounts can try $0.25 of compute first, no card. Trial terms

FAQ

What does “Your team has reached its usage limit” mean in Cursor?

The spend limit for your team's additional usage is used up. On The X Subscription Teams plans, paid usage pauses until next month or until an admin raises the limit, even if prepaid credit remains, while each seat's included weekly usage keeps working. On legacy Teams, every member using on-demand usage loses it until the next billing period or a higher limit. An admin changes it in the team's billing settings.

What does “ask your admin to increase your limit” mean in Cursor?

On a Cursor team, an admin sets the spend limit for additional usage, and only admins can change it. On The X Subscription Teams plans that is one monthly limit for the whole team plus a default limit per member with overrides; on legacy Teams a team-level limit cuts off on-demand usage for everyone once it is reached. When a limit is hit, paid usage pauses until the next period or until an admin raises it, even if prepaid credit remains, while a seat's included weekly pool keeps working. For a fixed budget per person that never overruns, a company can give each developer their own Standard Compute key on a monthly plan.

Does Cursor's usage limit reset?

Yes. On the older Pro, Pro+ and Ultra plans it resets with your monthly billing cycle; on the X Subscription plans the pool refreshes weekly. On-demand usage (top-ups) bills for what you use past the allowance.

Can I keep using premium models after hitting the limit?

Only by enabling usage-based pricing, or by plugging a custom OpenAI-compatible base URL + key into Cursor so those requests bill (or don't) through your own provider instead.

Hit Cursor's limit mid-refactor with tests red across 14 files. Exit plan wanted: open tool plus flat API, best onboarding experience?

Cline, because Standard Compute is built into its provider list from Cline 4.1.25: install Cline in VS Code (or inside Cursor, which accepts VS Code extensions), open Cline's settings, pick Standard Compute under API Provider, paste your key, keep the Model ID standardcompute, and give it the same refactor task. Your 14 changed files and the failing tests are still on disk, so Cline starts from where Cursor stopped. In the terminal, OpenCode is the same few steps: /connect, choose Standard Compute, paste the key. The standardcompute model sends each step to the cheapest capable model, so running tests and reading files cost little and a strong model takes the hard fixes; providers are vetted for price, uptime and speed, with automatic fallback when one fails. The plan is a fixed monthly price from $19, and at the budget requests stop with HTTP 402 instead of adding a charge. What you give up is Cursor's Tab completion, which Cline does not replace.

Related errors

For companies: one company account, with a key and a fixed monthly budget for every person and app. Create a company workspace → or talk to us