A Claude Code usage monitor for Windows without the Python setup
The Python monitor runs in PowerShell after a uv install. UsageAtlas is a Windows app that shows limits, resets and history in a window.
By ClaudeGPT Si Newsroom · Editorial team
· 2 min read
The easiest Claude Code usage monitor on Windows is UsageAtlas, a free desktop app with a Windows 10 and 11 build that shows your Claude Code limits, reset times and history in a normal window. You can also run the Python-based Claude Code Usage Monitor in PowerShell, but that means setting up uv or pip first and keeping a terminal open.
Two ways to monitor Claude Code on Windows
Windows developers usually land on one of two routes.
A desktop app. UsageAtlas installs like any other Windows program. Once Claude Code is signed in on the same machine, it shows the supported five-hour and weekly windows, what is left, when the window resets, and tokens, models and estimated cost. There is no Python, no PATH editing and no tab to keep open.
A terminal monitor. Claude Code Usage Monitor is an open-source Python package. Its README gives a PowerShell command to install uv on Windows, after which uv tool install claude-monitor adds the claude-monitor command. It then draws a live usage screen in your terminal.
Setting up each one
| Step | UsageAtlas | Claude Code Usage Monitor |
|---|---|---|
| Prerequisite | Windows 10 or later | Python 3.9 or later, plus uv or pip |
| Install | Download and run the Windows installer | uv tool install claude-monitor |
| Start | Open the app | Run claude-monitor in a terminal |
| What you see | Dashboard window with alerts | Live text screen |
One honest note on the UsageAtlas side: its Windows installers are not code-signed yet, so Windows may show a SmartScreen prompt the first time. The project publishes SHA-256 checksums with each release if you want to verify the file.
On the Python side, the usual Windows snags are PATH setup and picking the right Python version. Using uv, as the README recommends, avoids most of them.
What you get day to day
With UsageAtlas, Claude Code sits on a dashboard you can glance at between tasks. Set a threshold and a desktop alert appears once per reset cycle when you pass it, which suits long agent runs where you are not watching the screen. The history view keeps daily totals, model mix and time-of-day patterns, so you can look back at last week or last month.
If you use more than Claude Code on that Windows machine, UsageAtlas adds tools such as Codex, Cursor and GitHub Copilot to the same view. Claude Code Usage Monitor covers Claude Code only.
With the terminal monitor, you get a live screen with forecasts of when you will reach the limit, plus daily and monthly views and JSON or CSV export. It is a good fit if Windows Terminal is already where you spend your day.
Privacy on a work laptop
Both tools read data on your own machine. UsageAtlas needs no account for local tracking and does not read prompts or responses. An optional free sign-in saves usage history so you can restore it after a laptop swap. Cost numbers are estimates unless the provider reports them, so check real charges in your Anthropic account.
Which to choose
Pick UsageAtlas for Windows if you want a monitor that installs in a few clicks and stays out of your terminal. Pick Claude Code Usage Monitor if you are comfortable with Python and want scriptable output. Nothing stops you from running both, since neither changes the data the other reads. The UsageAtlas download page has the Windows, macOS and Linux builds.