The top Claude Code token usage monitor right now is UsageAtlas, a free desktop app that tracks tokens, models, estimated cost, limits and reset times without a terminal open. Below it sit two solid terminal tools and the command that ships with Claude Code, ranked by how much they tell you and how little effort they take.

How we ranked them

Every entry here is free. We scored them on four things a token watcher should do: show the numbers you care about, warn you before a limit, keep history past today, and cover the other coding assistants you use. Setup effort breaks ties.

1. UsageAtlas

UsageAtlas takes first place because it does all four jobs in one window. For Claude Code it shows tokens, requests, models and estimated cost, plus the supported five-hour and weekly windows with time to reset. You pick a threshold and get one desktop alert per reset cycle. The history view keeps daily totals, the model mix and the hours you work hardest, and you can open last month as a range.

It also reads Codex, Cursor, OpenCode, GitHub Copilot and more, so a day split across assistants adds up in one place. It runs on Windows, macOS and Linux, needs no account for local tracking, and does not read prompts or responses. It is open source under MIT.

Best for: anyone who wants token totals and limits visible all day.

2. claude-monitor in the terminal

The Claude Code Usage Monitor earns second. It is a Python package you install with uv or pip and launch as claude-monitor. Its live terminal screen tracks tokens, messages and cost against the current window and forecasts your pace. It can capture Claude Code's official rate limits through a status line hook, switch to daily or monthly views, and write JSON or CSV.

It loses ground on reach: it watches Claude Code only, and you need a terminal tab open to see it.

Best for: terminal users who want a live screen and scriptable output.

3. ccusage

ccusage is a command line reporter you run with npx ccusage@latest. It reads local data and prints token and cost tables by day, month or session, with a blocks view for Claude Code's five-hour windows. It reports when you ask rather than watching continuously, which is why it ranks below a live monitor here.

Best for: quick reports and JSON exports.

4. /usage, built into Claude Code

Claude Code's own /usage shows session cost, plan usage limits and activity stats, and /cost and /stats open the same view. It needs no install, which is its strength. It only answers when you run it and does not keep long-range history.

Best for: a quick look mid-session.

The ranking at a glance

Rank Tool Watches continuously History Other coding tools
1 UsageAtlas Yes, with desktop alert Yes Yes
2 Claude Code Usage Monitor Yes, in terminal Opt-in No
3 ccusage No Reads local logs Several CLIs
4 /usage No No No

A note on numbers

Token counts come from local data and provider reports, and dollar figures in these tools are estimates unless the provider supplies the cost. For billing, the Anthropic account is the record.

Which one to install

Start with UsageAtlas if you want a monitor you never have to remember to open; the Claude Code usage tracker page shows the views. Add Claude Code Usage Monitor if you also want a terminal pane or JSON for scripts. The tools read the same data without changing it, so running two costs nothing.