The best AI usage tracker for Windows is UsageAtlas, a free, open-source desktop app that runs on Windows 10 and Windows 11 and sits in the system tray. It reads Claude Code, Codex, Cursor and the other coding tools on the same PC and shows tokens, estimated cost, usage limits, reset times and history in one window.
This guide walks through the install, what appears on first launch and the few settings worth changing.
Install on Windows 10 or 11
- Download the Windows installer from the UsageAtlas download section.
- Run it. The build is not code-signed yet, so Windows SmartScreen may stop it. Choose More info, then Run anyway.
- Check that the tools you want to track are signed in on this PC: Claude Code with your Pro or Max account, and the Codex CLI with your ChatGPT account.
- Open UsageAtlas. It finds the supported tools and fills the dashboard.
No UsageAtlas account is needed for any of this. The app reuses the sign-ins your coding tools already stored, and some credit-based tools ask for a key in Settings instead.
What you see on first launch
The tray icon is the quick view. The full window is where the history lives.
| Where | What it shows |
|---|---|
| Tray | How much of each usage window is left and when it resets |
| Today | Current windows for Claude Code, Codex and other tools that report them |
| History | Tokens and estimated cost by day, project, session and model |
| Insights | Your busiest hours and weekdays |
For Claude Code, the limit percentages cover the five-hour and the weekly window. Those limits are shared with the Claude apps, so time on claude.ai shows up there too. Token history, on the other hand, comes from Claude Code's local logs on this PC. For Codex you also get the credit balance it reports.
What you get depends on the tool. Tools that report a usage window show limits and resets. Tools that only write local session files show tokens and history but no limit.
Settings worth changing
Usage alerts. Pick a window, such as the Claude five-hour window, and set the remaining capacity that should warn you. UsageAtlas sends one desktop notification per window per reset cycle, then stays quiet until the window resets. The app has to be running for this, which is why it lives in the tray and can launch at login.
Cloud save. Sign in with a free Google or GitHub account if you want your history saved and restored on a new PC. Skip it and everything stays local.
Anonymous install count. It is separate from cloud save and can be switched off on its own.
Why a tray app instead of the built-in commands
Claude Code has /usage and the Codex CLI has /status. Both are good for a glance inside a session. They disappear when you close the terminal, they cover one tool each, and they do not keep last month's numbers. A tracker on Windows fills that gap without changing how you work. Cost figures in UsageAtlas are estimates from token counts, not a bill, so check your provider's billing page before any money decision.
If you only use Claude and want the smallest possible tray meter, usage-monitor-for-claude is a portable single EXE that does just that. For Claude plus Codex, Cursor and the rest in one place, get UsageAtlas for Windows.
Questions
Is UsageAtlas free on Windows? Yes. It is free and open source under the MIT license.
Does it read my prompts? No. It works from usage totals such as tokens, requests, models and reported limits. Prompts and responses are not read.
Does it also run on Mac and Linux? Yes. The macOS and Linux builds are on the same download page.