Cursor usage limit reached: what to do next

Kayvan Zahiri · October 18, 2026

When Cursor tells you that you have hit your usage limit, you see a notification in the editor. Your options are to wait for the next reset, enable more paid usage, upgrade, or keep the task going in Claude Code or Codex. Cursor's included usage is not a five-hour window like Claude Code's session limit: it is a pool that refreshes on a weekly or monthly cycle, depending on which Cursor plan you are on.

Which plan you are on

Cursor's usage-limits help page, read on October 18, 2026, describes two kinds of plan.

The X Subscription (Free, Plus, Premium, Super, Ultra, and Teams seats): each paid plan includes one weekly pool of usage for Cursor models. Third-party models are not in that pool. On Premium and above they are billed at API list price from prepaid credit.
Legacy Cursor plans (Hobby, Start, Pro, Pro+, Ultra, and Teams Standard and Premium seats): included usage is split into two monthly pools, Cursor Models and Other Models (third-party models, charged at provider prices). Pro, Pro+, Ultra, and Teams include both pools. Start covers the Cursor Models pool only.

On either kind of plan, the model you pick affects how quickly included usage is consumed. Unused included usage does not roll over on either kind of plan.

Where to see what you have left

On The X Subscription, open Usage at grok.com/dashboard. It shows how much of the weekly pool you have used, the next reset date, and prepaid credit. Editor settings show the same remaining usage.
On a legacy Cursor plan, open the Spending tab. It shows real-time usage for both pools, remaining allowance, and any on-demand charges. The reset date is on that tab. For teams, every member's usage resets together on the team billing cycle.

Check that page before you change plans or turn on paid usage. The reset date answers "when does it come back," which is the question most people search after the notification.

What happens when you hit the limit

You see a notification in the editor. Cursor's models-and-pricing page, also read on October 18, 2026, says requests are never downgraded in quality or speed when you reach the limit.

On The X Subscription: keep working from prepaid credit, wait for the weekly pool to refresh, or upgrade. Buy credit when you choose, or turn on Auto Top-up. A monthly additional usage limit can cap how much paid additional usage you consume each month.
On a legacy plan: enable on-demand usage (pay-as-you-go at the same API rates) or upgrade to a higher plan.

On individual plans, requests made with your own API key do not draw from either included pool or from prepaid credit; your provider bills you for the model cost. On Teams and Enterprise, own-key requests still carry Cursor's token rate.

Keep working without waiting

If you already use Claude Code or Codex, you can finish the task there while Cursor's pool resets. The files Cursor already changed stay in the project folder. In that folder:

git status
git diff --stat
git diff

You do not need to commit. Write a short note the next agent will read first. Use your own task. This shape is enough:

Task: (what you asked Cursor for)
Done: (what landed; see the diff)
Not done: (what is left)
Next step: (the one thing to do first)
Stopped because Cursor hit a usage limit. Do not redo finished work.

Open Claude Code or Codex on the same folder, start a new chat, and paste the note as the first message. Ask it to repeat the task and the next step before it edits anything. A chat that already has history is the wrong place in Cursor when you come back later: start a new one.

BuildGist can carry that task instead of the note. When you start a new chat in Claude Code or Codex in the same project, a BuildGist card offers Cursor's task. Choose Continue and the chat starts with that context, or Start fresh to skip it. Claude Code takes the context on a new session. Moving a task among Claude Code, Cursor and Codex is in how to keep context across agents.

Which of these is your situation

You just need the reset date. Check Usage on The X Subscription, or the Spending tab on a legacy plan.
You want to keep typing in Cursor now. Enable on-demand usage (legacy) or use prepaid credit (The X Subscription), or upgrade.
You are on Start and only see one pool. That matches the docs: Start covers Cursor Models only.
You use your own API key on an individual plan. Those requests do not draw from the included pools.
You would rather finish in another agent. Read the diff, write the note, or choose Continue in Claude Code or Codex.

If Claude Code or Codex is the one at its limit, see you’ve hit your session limit in Claude Code or you’ve hit your usage limit in Codex. Those limits are five-hour or weekly windows, not Cursor's billing-cycle pools.

Sources

Cursor usage and limits, checked October 18, 2026.
Cursor models and pricing, checked October 18, 2026.

What you need

A Mac with Apple silicon and macOS 12 or later.
Claude Code, Cursor or Codex.
A Git project. No commit, push, remote or GitHub repository is needed.
A GitHub account, to sign in. BuildGist does not access your GitHub repositories.

Codex needs you to approve BuildGist once, in Codex. BuildGist shows the steps. Setup is in Getting started.

To explain a run, your computer sends BuildGist what that run needs, and BuildGist passes it to Anthropic. BuildGist does not keep this material. It does not send your whole repository, files the run did not change, or files named like secrets, such as .env files and keys. It keeps the explanation and short cited excerpts of changed code, at most 12 lines each. Secret masking is best-effort. Privacy has the full list.

Every account gets 7 days of BuildGist Pro free, with no card. The 7 days start at your first explanation or Continue handoff. Nobody is charged when the trial ends. After that, BuildGist Pro is $12 per month, plus any applicable tax shown at checkout. See pricing.

Try BuildGist

Apple silicon, macOS 12 or later. United States, 18 or older.

Questions: kayvanandre@gmail.com.