Cursor usage vs Claude Code: where each one shows it
Cursor reports usage on its dashboard, Claude Code in /usage, and UsageAtlas puts both in one free desktop view.
By ClaudeGPT Si Newsroom · Editorial team
· 2 min read
Cursor usage vs Claude Code usage comes down to where each one reports it: Cursor puts it on its web dashboard and in an editor setting, while Claude Code shows it in the terminal with the /usage command. If you use both, UsageAtlas, a free desktop app, puts the two side by side so you do not have to piece the day together yourself.
Same work, two meters
Plenty of developers keep Cursor open for editing and run Claude Code in a terminal for longer agent tasks. Each tool keeps its own meter, and neither knows about the other. So a question as simple as "how much AI did I use today?" needs two answers added up by hand.
Where Cursor shows usage
- Web dashboard. On legacy plans, the Billing & Invoices page lists included usage and on-demand usage. Cursor's help pages point newer subscriptions to a different page, so check the one for your plan.
- In the editor. A Usage summary setting, set to Always, keeps usage visible in the chat pane. Search Cursor Settings for "usage summary", since its location has moved.
Where Claude Code shows usage
- The
/usagecommand. Anthropic's docs say it shows token usage for the current session. On Pro, Max, Team or Enterprise plans it also shows plan usage bars and a breakdown of what counts against your limits. - A local view. Anthropic notes the breakdown is computed from session history on that machine, so use from other devices or claude.ai is not included.
Side by side
| Cursor | Claude Code | |
|---|---|---|
| Main place to look | Web dashboard | /usage in the terminal |
| Quick view while working | Usage summary setting | /usage or the status line |
| Billing source of record | Cursor account | Your Claude plan or Console account |
| Sees the other tool | No | No |
One view for both
UsageAtlas fills that last row. It reads your signed-in Cursor desktop session for plan, Auto + Composer and API usage, and it reads Claude Code's five-hour and weekly windows plus local activity using the Claude sign-in already on your computer. Both land in one dashboard with daily history, and a filter shows either tool on its own when you need it.
You can set a threshold for a supported usage window and get one desktop alert per reset cycle, so a long Claude Code run does not surprise you while you are busy in Cursor. The app is free and open source, runs on Windows, macOS and Linux, needs no account for local tracking and does not read prompts or responses. Its cost figures are estimates, so check billing in each provider's account.
When you do not need it
If you only use one of the two tools, its own view is enough. Cursor's dashboard and Claude Code's /usage each do their own job well. The Cursor tracking guide is worth a read once you start mixing them.
FAQ
Does Cursor's dashboard include Claude Code usage? No. Cursor's dashboard covers usage inside Cursor, and Claude Code reports its own usage through /usage and your Claude account.
Can I see Cursor and Claude Code usage together? Yes, with UsageAtlas. It shows both in one desktop view and lets you filter to either one.