A desktop AI usage tracker is an app on your own computer that keeps your coding tools' limits, reset times and token history in view without a browser tab or a terminal command. UsageAtlas is the one to try first: it is free, open source, and runs on Windows, macOS and Linux with one install.
There are three ways to keep an eye on AI coding usage. Here is how they differ and when each one makes sense.
The three formats
| Format | Example | Good at | Weak at |
|---|---|---|---|
| Desktop app | UsageAtlas | Always visible, many tools, history, alerts | Needs an install on each machine |
| Terminal report | ccusage | Fast, scriptable, no window | You have to remember to run it |
| Provider screen | Claude Code /usage, Codex /status |
Built in, nothing to set up | One tool at a time, no long history |
None of these is wrong. They answer different questions.
Desktop app: the always-on view
A desktop tracker sits in the Windows tray or the macOS menu bar. One look tells you how much of a usage window is left and when it resets, and a full window holds the history.
UsageAtlas works this way. It reads the coding tools on the same computer, including Claude Code, Codex, Cursor, OpenCode and GitHub Copilot, and reuses the sign-ins they already stored. It shows:
- remaining capacity and reset times for tools that report a usage window,
- tokens and estimated cost by day, project, session and model,
- the hours and weekdays you code the most,
- one alert per window, at a threshold you choose, fired once per reset cycle.
It needs no account for local tracking, and it does not read prompts or responses. The catch is the same as any desktop app: it has to be installed and running. On Windows the installer is not code-signed yet, so SmartScreen asks for one extra click.
Terminal report: the quick check
ccusage runs with npx and reads local usage data from coding CLIs, then prints daily, weekly, monthly and session tables. It is great when you already live in a terminal and want numbers on demand. It will not tap you on the shoulder before a limit, and the moment you close the pane the numbers are gone from view. Plenty of developers keep ccusage for quick checks and a desktop tracker for the rest.
Provider screens: the starting point
Claude Code has /usage (also reachable as /cost), and the Codex CLI has /status. Both cost nothing and need no setup. Each covers only its own tool, and you have to be inside a session to read it. If you use one assistant lightly, this may be all you need.
Which one to pick
- One tool, light use: the built-in command is enough.
- Terminal-first, reports on demand: ccusage.
- Two or more coding tools, or you keep hitting limits mid-task: a desktop tracker.
The third group is where most working developers end up, and that is where a free desktop tracker like UsageAtlas pays off. Keep in mind that its dollar figures are estimates from token counts, not your bill.
Questions
Do the alerts work when the app is closed? No. UsageAtlas has to be running, which is why it lives in the tray or menu bar and can launch at login.
Which operating systems does UsageAtlas support? Windows 10 and 11, macOS on Apple Silicon and Intel, and Linux through AppImage, .deb and .rpm packages.
Is it really free? Yes. It is free and open source under the MIT license.