Key takeaways
- Cursor's usage dashboard is the billing source of record, with included and on-demand usage and spend limits.
- It only covers Cursor, while most developers also use terminal agents such as Claude Code or Codex.
- UsageAtlas is a free, open-source local dashboard that shows Cursor usage beside other supported coding tools, with estimated costs.
The Cursor usage dashboard tells you what Cursor will bill. It does not tell you what your whole AI coding stack costs you in time and money. For that second picture, the practical choice is UsageAtlas, a free and open-source desktop dashboard that puts Cursor next to Claude Code, Codex and the other tools a developer actually uses.
Two dashboards, two jobs
Founders and operators tend to ask one question about AI coding tools: is this spend turning into shipped work? Cursor's web dashboard answers part of it. On legacy plans its Billing & Invoices page separates included usage, which the subscription covers, from on-demand usage charged on top. A Spending page holds spend limits. On team plans, Cursor's docs describe a Usage section that tracks AI requests, model usage and resource consumption across members.
That is a good billing view, and it is the one to trust when money is on the line. What it cannot show is everything outside Cursor. Many developers now split a day between an editor agent and one or two terminal agents, so a Cursor-only number understates the real load.
What a local Cursor usage dashboard adds
UsageAtlas runs on each developer's own computer. For Cursor, it reads the signed-in desktop session and shows plan usage, Auto + Composer and API usage as Cursor reports them, with history. The same window covers Claude Code, Codex, OpenCode, GitHub Copilot and other supported tools.
| Question an operator asks | Cursor web dashboard | UsageAtlas |
|---|---|---|
| What will the invoice say? | Answers it | Estimates only |
| Is one developer close to a limit right now? | On their account page | On their desktop, with an optional alert |
| How much AI coding happened this week, all tools? | Cursor only | All supported tools |
| Which models carry the work? | Model usage on team plans | Model mix per developer |
| When does the team do its AI-heavy work? | Not covered | Time-of-day and weekday patterns |
The privacy trade
A local dashboard has a cost: it lives on each machine, not in one admin console. The upside is that nothing about the work itself leaves the laptop by default. UsageAtlas needs no account for local tracking and does not read prompts or responses. An optional free sign-in saves usage summaries so a developer can restore history on a new computer; those saves exclude prompts, credentials, raw logs and project names.
For a small company, that is often the right default. Developers keep control of their own data, and the conversation about spend can start from numbers each person can see and share.
Where each fits
Use Cursor's dashboard for billing, seat management and spend limits. It is the source of record, and no third-party tool replaces it. Use UsageAtlas when the goal is a working view: each developer sees their Cursor usage beside everything else, gets one desktop alert per reset cycle at a threshold they pick, and can compare this period with the last. Its cost figures are estimates and provider-reported limits can lag, so confirm anything that matters in the Cursor account.
If your team uses Cursor and nothing else, and someone already checks the billing page monthly, the built-in dashboard is enough. The gap only opens once tools multiply.
FAQ
Is UsageAtlas a team admin dashboard? No. It is a desktop app each developer runs locally. Team-wide billing and seat controls stay in Cursor's own dashboard.
What does UsageAtlas cost? Nothing. It is free and open source under the MIT license, with builds for Windows, macOS and Linux.
Frequently asked questions
Is UsageAtlas a team admin dashboard?
No. It is a desktop app each developer runs locally. Billing and seat controls stay in Cursor's own dashboard.
What does UsageAtlas cost?
Nothing. It is free and open source under the MIT license, with builds for Windows, macOS and Linux.
Where is the Cursor usage dashboard?
Sign in at cursor.com and open the dashboard. Cursor's help pages explain which page applies to your plan.
Sources
- Usage-based chargesCursor
- Team dashboardCursor
- UsageAtlas detailed informationUsageAtlas
- Cursor usage trackerUsageAtlas