UsageAtlas

One desktop dashboard for your AI coding usage.
See quota, resets, tokens, requests, and cost across Codex, Claude, Cursor, and OpenCode. No account required.

Download for Windows, macOS, or Linux · All releases

Use UsageAtlas without an account to track usage on your computer. If you want to keep a copy of your usage history
and restore it after changing or losing a computer, you can create a free account and use cloud save.

Screenshots

Install

Get an installer from usageatlas.com or the
releases page, then:

• Windows — run the .exe installer. Builds are not Authenticode-signed yet, so choose More info → Run anyway at the SmartScreen prompt.
• macOS — open the .dmg and drag UsageAtlas into Applications. Builds are signed and notarized.
• Linux — run the .AppImage, or install the .deb or .rpm.

Every asset is listed with its SHA-256 in SHA256SUMS on the release. macOS and Windows update themselves in the background.

What it reads

UsageAtlas reuses the credentials the tools already keep on your machine. Nothing else is needed to sign in.

• Codex — talks to the installed, signed-in Codex CLI through its official local app-server API. The OAuth token is never read.
• Claude — reads CLAUDE_CODE_OAUTH_TOKEN or .credentials.json in your Claude config directory, then queries the OAuth usage endpoint.
• Cursor — reuses the signed-in desktop session from Cursor's local state database for account limits plus 90 days of per-request token, model, and cost history.
• OpenCode — reads the local OpenCode database for per-step token, request, project, model, and cost analytics.

Four more providers are on the way. A provider only ships once it has complete authentication, structured error
handling, and deterministic adapter tests.

Highlights

• Today view with capacity meters, reset times, plan details, credits, and hourly activity
• History and insights across 7, 30, and 90 days by project, session, model, and tool
• Usage alerts that fire a native notification before you run into a limit
• Tray presence, launch at login, and system/light/dark themes
• Local tracking with no account required
• Optional free account to save usage history to the cloud and restore it on another computer
• Sealed local history: completed days are stored on disk so past usage survives restarts and provider outages
• Sandboxed renderer with no Node.js access, an allowlisted preload API, ASAR integrity, and Electron fuses

Privacy

Provider data is read from local files and provider APIs. Completed-day usage and capacity
snapshots are stored in a local history database in the app data directory. Without signing in to
UsageAtlas, your usage history stays on your computer.

If you choose a free account, cloud saves store usage totals, estimated costs, hourly activity, public model
breakdowns, and limits and plan information under that account. Project and session names, file paths, prompts,
responses, raw logs, and coding-tool credentials are not included. Cloud saves contain usage summaries,
so restoring them does not restore every local project or session detail.

The optional anonymous install count is separate from cloud save. It never includes usage figures or your
account name or email, and you can switch it off in Settings. Diagnostics are redacted before they are shown or copied.
See the privacy policy and terms of use.

Optional free cloud save

1. Open Settings → Cloud save in the desktop app.
2. Sign in with Google or GitHub to create or use a free UsageAtlas account.
3. Pending usage saves automatically once an hour while the app is running. You can turn off Save automatically
   and use Save to cloud whenever you want. A previous automatic-save choice is remembered on this computer.
4. On another computer, sign in to the same account and choose Restore from cloud.

Only successfully saved history can be restored. Check that saving has completed before removing local app data
or replacing your computer. Signing out stops future saves but does not delete existing cloud history. To request
account and cloud-history deletion, email [email protected].

Build from source

Requirements: Bun 1.3.14 and Node.js 22.13+.

git clone https://github.com/SRX9/UsageAtlas.git
cd UsageAtlas
bun ci
bun run desktop:start

bun run check runs lint, typecheck, tests, and the build. bun run desktop:make produces installers for the current
platform with Electron Forge; unsigned builds need no credentials.

The repo is a Bun + Turborepo workspace: the Electron app lives in apps/desktop, shared schemas and fixtures in
packages/contracts, and build helpers in tooling.

Releases

Every push to main ships a release. CI takes the version in apps/desktop/package.json, moves the patch number to
the first one that is not published yet, records that back on main, then builds, signs, and notarizes every
platform, tags desktop-v<version>, and publishes the installers, SHA256SUMS, and the update feeds the in-app
updater consumes. Write a new major or minor version there by hand and it releases as written instead.

See CONTRIBUTING.md to contribute and SECURITY.md to report a vulnerability privately.

Acknowledgements

Inspired by CodexBar by Peter Steinberger. Charts are vendored from
Dither Kit.

License

Source code is available under the MIT License. The UsageAtlas name and logo are not covered by it — see
TRADEMARKS.md.