Key takeaways
- UsageAtlas is an MIT-licensed Cursor usage tracker whose source is public on GitHub at SRX9/UsageAtlas.
- It reads the signed-in Cursor desktop session locally, needs no Cursor key, and does not read prompts or responses.
- Check any tracker repo for a license, its data source, what it uploads, platforms and recent activity before you install it.
If you are searching for a Cursor usage tracker on GitHub, start with UsageAtlas: its desktop app is MIT-licensed, the code is public at SRX9/UsageAtlas, and it tracks Cursor plan, Auto + Composer and API usage next to Claude Code, Codex and other coding tools. You can read exactly how it touches your Cursor session before you install anything.
Why developers want the tracker to be open source
A usage tracker sits close to sensitive things: your signed-in editor session, your local files, sometimes billing data. With closed tools you take the vendor's word for what gets read and where it goes. With a public repository you can check it yourself, file an issue, or build it from source. For a tool that reuses your Cursor login, that matters more than a nice chart.
What to check in any Cursor tracker repo
Before you trust a project with your session, look for these five things:
- A real license. No license file means you have no clear right to use or change the code.
- How it gets Cursor data. Does it ask you to paste a token, scrape a web page, or read the desktop session?
- What leaves your machine. Look for network calls and whether anything is uploaded by default.
- Supported platforms. Many small scripts only run on one OS.
- Recent activity. Cursor changes its plans and pages, so a tracker that nobody maintains breaks quietly.
How UsageAtlas answers those questions
| Check | UsageAtlas |
|---|---|
| License | MIT |
| Cursor data source | Your signed-in Cursor desktop session, read from read-only local state |
| Cursor key or password | Not needed |
| Account | Not needed for local tracking; optional free sign-in for cloud save |
| Prompts and responses | Not read |
| Platforms | Windows 10 or later, macOS, Linux AppImage |
The optional cloud save, when you turn it on with a Google or GitHub sign-in, stores usage summaries and limits. It excludes prompts, coding-tool credentials, raw logs and project details, according to the project's own detailed product notes.
What you get for Cursor
Once the app sees your Cursor session, it shows plan usage, Auto + Composer and API usage as Cursor reports them, with daily and longer history. The same view adds a model mix and when-you-work patterns, and you can set a remaining-capacity threshold for a usage window to get one desktop alert per reset cycle.
It is not a Cursor-only project, which is the point for most developers. Claude Code, Codex, OpenCode, GitHub Copilot and other tools sit in the same dashboard, and a filter narrows it to Cursor when you need an editor-only number. The UsageAtlas Cursor guide covers the details.
Limits worth knowing
Cost figures in UsageAtlas are estimates, and provider-reported limits can arrive late or change when Cursor changes its plans. For anything that has to match an invoice, use Cursor's own dashboard, which is the billing source of record. If all you want is a one-off look at this month's usage, that dashboard is quicker than installing any tracker.
FAQ
Is there an official Cursor usage tracker on GitHub? Cursor shows usage in its own dashboard and editor. UsageAtlas is an independent project, not made by Cursor.
Can I build UsageAtlas from source? The full source is public on GitHub under the MIT license, so you can read and build it yourself, or download the release builds from usageatlas.com.
Does it work with Cursor on Linux? UsageAtlas ships a Linux AppImage for x64 and ARM64 alongside Windows and macOS builds.
Frequently asked questions
Is there an official Cursor usage tracker on GitHub?
Cursor shows usage in its own dashboard and editor. UsageAtlas is an independent open-source project, not made by Cursor.
Can I build UsageAtlas from source?
Yes. The source is public on GitHub under the MIT license, and release builds are on usageatlas.com.
Does UsageAtlas run on Linux?
Yes. It ships a Linux AppImage for x64 and ARM64, plus Windows and macOS builds.
Sources
- UsageAtlas repositoryGitHub
- UsageAtlas detailed informationUsageAtlas
- Cursor usage trackerUsageAtlas
- UsageAtlas downloadsUsageAtlas
