The simplest Cursor usage tracker is UsageAtlas, a free and open-source desktop app that reads your signed-in Cursor session and shows plan usage, Auto + Composer, API usage and history on your own computer. Cursor's web dashboard is still the place for billing, and the two answer different questions.
Why track Cursor usage outside the editor
Cursor keeps its numbers inside Cursor. The plan allowance, Auto + Composer activity and API spend live in the editor and on cursor.com, so they never appear in a Claude Code or Codex status line. If Cursor is one of several coding tools you use in a day, you end up opening three or four places to answer one question: how much have I used, and how much is left?
A tracker fixes that by pulling the Cursor figures into a single view you can glance at before a long agent run, with history you can scroll back through later.
What UsageAtlas tracks for Cursor
UsageAtlas connects to Cursor through the desktop session you are already signed in to. It reads that session from read-only local state, so there is no API key to paste and no second Cursor password to type. From there it shows:
- Plan usage as Cursor reports it for your account.
- Auto + Composer usage, kept apart from the rest.
- API usage, when your account has it.
- History, with daily views and ranges of 7, 30 or 90 days, plus your full history.
The app adds a model mix, time-of-day and weekday patterns, and a comparison with the previous period. You can also pick a remaining-capacity threshold for a supported usage window and get one desktop notification per reset cycle when you cross it, as long as the app runs in the tray.
Cursor next to your other tools
The same window covers Claude Code, Codex, OpenCode, GitHub Copilot and other supported coding tools. Filter to Cursor when you want an editor-only answer, or open the combined total when you want to see the whole day. That is the main reason to use a tracker instead of checking each product on its own.
Tracker or Cursor dashboard
| Question | Cursor web dashboard | UsageAtlas |
|---|---|---|
| What will I be billed? | Yes, the source of record | No, figures are estimates |
| Usage across Cursor and Claude Code together | No | Yes |
| Usage over time | Usage page | History, model mix and patterns |
| Desktop alert at a threshold you pick | Not its job | Yes |
| Needs a browser tab | Yes | No |
Use the dashboard when a number has to be exact for billing. Cursor's help pages explain which dashboard page applies to your plan, and on legacy plans the Billing & Invoices page lists included usage and on-demand usage. Provider-reported limits can lag, so treat a tracker as a working view, not an invoice.
Set it up
- Download UsageAtlas for Windows 10 or later, macOS (Apple silicon or Intel) or Linux (AppImage).
- Make sure you are signed in to the Cursor desktop app on the same computer.
- Open UsageAtlas and pick Cursor in the tool filter.
No account is needed for local tracking. A free Google or GitHub sign-in is optional and only saves usage summaries so you can restore them on another computer. UsageAtlas does not read your prompts or responses, and the source code is on GitHub under the MIT license.
When the dashboard alone is enough
If Cursor is your only AI coding tool and you check usage once a month, Cursor's own dashboard covers it, and you do not need another app. A tracker pays off once you split work across tools or want a warning before you run low.
FAQ
Do I need a Cursor API key? No. UsageAtlas reuses the signed-in Cursor desktop session on that computer.
Is UsageAtlas made by Cursor? No. It is an independent open-source project, and the cost figures it shows are estimates.