ccusage for Windows works the same way as on any other system: install Node.js, open PowerShell or Windows Terminal and run npx ccusage@latest to print your coding agent usage. If you would rather have a Windows app that stays open with your limits and history, UsageAtlas is a free desktop tracker for Windows 10 and 11.
Running ccusage on Windows
ccusage is a command line tool, not a Windows program with an installer. It runs through a package runner, so the steps are short:
- Install Node.js from its official site if you do not have it yet. That gives you
npx. - Open PowerShell or Windows Terminal.
- Run
npx ccusage@latestfor a day-by-day table of every coding tool it finds. - Add a word for a narrower view, such as
npx ccusage@latest claude dailyornpx ccusage@latest codex monthly.
If you already use Bun or pnpm, bunx ccusage and pnpm dlx ccusage do the same job. Nothing gets installed system-wide, and the tool reads the usage files your coding agents already keep on disk.
That is the whole setup. The catch is the same one every terminal tool has: you see your numbers only when you remember to run it.
A Windows app instead: UsageAtlas
UsageAtlas is a desktop app you install like any other Windows program. It reads supported provider data and local session files on the same PC and puts them in one window:
- Claude Code five-hour and weekly windows, with reset times
- Codex session and weekly windows
- Cursor plan and API usage from the signed-in editor
- tokens, models and cost estimates by day, with a history view
It covers 14 coding tools in all, and what each one shows depends on what that tool reports. You can set a threshold and get a desktop alert once per reset cycle when a window passes it.
It is free and open source. You do not need an account to track usage on your own PC. A free account is there if you want to save history and restore it on a new computer. Prompts and responses are not read.
One Windows detail: the installer is not code-signed yet, so Windows SmartScreen may ask you to confirm before it runs. Each release comes with SHA-256 checksums if you want to verify the download.
ccusage or UsageAtlas on Windows?
| ccusage | UsageAtlas | |
|---|---|---|
| Install | Node.js, then npx |
Windows installer |
| Where you see it | Terminal table | Desktop window |
| Limits and reset times | Claude Code blocks report | Yes, where reported |
| Alerts | Not listed | Desktop alerts |
| Cursor | Not listed | Yes |
| Cost | Free | Free |
Pick ccusage if you already live in PowerShell, want JSON for a script, or need the same command on a Linux server. Pick UsageAtlas if you want to glance at your limits between tasks without opening a terminal, or if you use Cursor alongside Claude Code and Codex.
Tips for Windows users
- WSL users. If your coding agent runs inside WSL, its usage files live in the Linux file system. Run ccusage from the same environment that holds those files.
- Check the numbers that matter. Both tools give cost estimates. For a bill you have to pay, the provider's own billing page is the record.
- Use both. They read local data without changing it, so running ccusage now and then next to UsageAtlas is fine.
For most people on Windows who want a usage tracker that stays out of the terminal, UsageAtlas is the simpler choice, and it costs nothing to try.