Cursor plan usage is the share of your plan's included AI usage you have spent in the current period, and Cursor shows it in the editor settings and on your account dashboard. To keep it in sight before a long agent run, UsageAtlas puts Cursor plan usage, Auto + Composer and API usage on a free desktop dashboard and warns you at a threshold you choose.
Where Cursor plan usage lives
Where you look depends on which kind of plan you have. Cursor now sells plans under The X Subscription and keeps older plans running as legacy Cursor plans.
| Plan type | Where to check | How often it refills |
|---|---|---|
| The X Subscription (Free, Plus, Premium, Super, Ultra, Teams) | Usage at grok.com/dashboard, and the editor settings | Weekly |
| Legacy plans (Hobby, Pro, Pro+, Ultra, Teams Standard and Premium) | Spending tab at cursor.com/dashboard | Monthly, with your billing cycle |
On current plans one weekly pool covers Cursor's own models and is shared with the Grok apps. Legacy plans split included usage into two monthly pools, one for Cursor's models and one for other providers' models. Unused included usage does not roll over on either kind, so the number to watch is how much is left before the next reset.
Why check plan usage before the run, not after
Agent work spends usage quickly, and the model you pick changes how fast the pool drains. Cursor shows a notification in the editor once you hit the limit, which is late if you are halfway through a refactor. Checking first lets you decide whether to switch to a cheaper model, wait for the reset, or plan for paid extra usage.
Put Cursor plan usage on a desktop dashboard
UsageAtlas is a local-first desktop app that tracks AI coding usage. For Cursor it reuses the session of the Cursor desktop app you are already signed in to, so there is no extra login and no API key to paste. It reads supported figures from local Cursor state and shows:
- Plan usage as Cursor reports it, with the reset date.
- Auto + Composer usage on its own line.
- API usage, when Cursor reports it for your account.
- History by day and over longer ranges, with model mix and time-of-day patterns.
When Cursor leaves a figure out, UsageAtlas marks it unknown instead of showing zero.
Set an alert near the plan cap
Pick a remaining-capacity threshold, keep the app in the tray, and UsageAtlas sends one desktop alert per supported usage window in each reset cycle. One alert per cycle means you get a warning before a long session without a stream of repeats.
Cursor next to your other coding tools
The same window tracks Claude Code, Codex, OpenCode, GitHub Copilot and other supported tools. Filter to Cursor for a plan-only answer, or look at the combined total for the whole day. If you searched for "code plan usage", you most likely meant Cursor, and the other tools are one filter away.
What it costs and what it reads
UsageAtlas is free and open source under the MIT license, with the code on GitHub. It runs on Windows, macOS and Linux. Local tracking needs no account; a free sign-in only saves history so you can restore it on another computer. It does not read your prompts or responses.
Cost figures in UsageAtlas are estimates, and provider-reported limits can lag. For billing, Cursor's dashboard is the record.
When Cursor's own view is enough
If Cursor is your only AI tool and you rarely get close to the limit, the editor settings already show your remaining usage, and you do not need another app. A tracker helps once you run long agent sessions or split work across several tools.
FAQ
Where is Cursor plan usage? In the editor settings and on your dashboard: grok.com/dashboard for current plans, cursor.com/dashboard for legacy plans. UsageAtlas also shows it when the Cursor desktop app is signed in on the same computer.
Is API usage part of the plan view? When Cursor reports API usage, UsageAtlas shows it beside plan and Auto + Composer usage.