ccusage for Cursor: why it is missing and what to use instead

There is no ccusage for Cursor today: Cursor is not on the list of tools ccusage reads, so its reports leave your editor usage out. The closest match is UsageAtlas, a free, open-source desktop app that reads Cursor plan, Auto + Composer and API usage from your signed-in Cursor session and shows it next to Claude Code and Codex.

Why ccusage skips Cursor

ccusage builds its reports from usage files that command line coding agents write to disk. Its README lists Claude Code, Codex, OpenCode, Amp, Droid, Gemini CLI, GitHub Copilot CLI, Kilo, Kimi and others. Cursor is not in that list, so npx ccusage@latest will not show your Cursor numbers.

That leaves Cursor users who also run Claude Code or Codex with split totals: one figure in the terminal, another somewhere in the editor.

Ways to track Cursor usage, ranked

1. UsageAtlas

UsageAtlas is the pick if you want Cursor in the same view as your other coding tools. It reuses the Cursor desktop session already signed in on your computer, so you do not paste an API key or log in a second time. From there it shows:

• plan usage, Auto + Composer and API usage
• history over time, with a filter for Cursor alone or the combined total
• the same dashboard for Claude Code, Codex, OpenCode and 10 more tools

You can set a threshold and get one desktop alert per reset cycle when a usage window passes it, which helps before a long agent run.

It is free and MIT licensed, needs no account for local tracking and does not read prompts or responses. It runs on Windows, macOS and Linux. Provider-reported limits can lag, and cost figures are estimates, so confirm exact billing in your Cursor account.

2. Cursor's own usage page

Cursor's docs say your remaining usage and next reset date appear in the editor settings and on the Usage page of your account dashboard. That is the record for billing and the right place to settle a disputed number. It covers Cursor only, though, so you still need something else for Claude Code or Codex.

3. ccusage, for everything except Cursor

ccusage is still useful in a Cursor setup. If you run Claude Code or Codex in Cursor's terminal, those CLI agents write their own usage data, and ccusage can report it. You just will not see the editor's own usage in that table.

Quick comparison

A setup that covers it all

1. Install UsageAtlas and let it read the Cursor session on your machine.
2. Let it pick up Claude Code and Codex too, if you use them.
3. Set an alert threshold so a window near its limit gets your attention.
4. Keep npx ccusage around for terminal reports or JSON exports from your CLI agents.

This way you get one place to look during the day and a terminal tool for the moments a script needs raw numbers.

When this is overkill

If Cursor is the only AI coding tool you use and you check usage once a month, the Cursor account page may be all you need. A tracker earns its place when you use more than one tool or keep hitting plan limits mid-task.