Is there a built-in way to see Claude Code usage?

Yes, the /usage command shows each window and its reset time for the signed-in account.

Can I track usage across several Claude accounts?

The built-in tools show one account at a time. AI Cooldown shows all of them side by side, with Codex accounts too.

Does AI Cooldown see my conversations?

No. It reads the usage endpoint, which returns percentages, reset times and the account email. Signed-in tokens are encrypted at rest and never sent back to the browser; without signing in they stay in your browser.

updated September 21, 2026

How to check and track your Claude Code usage

The quickest check is the /usage command inside Claude Code, which shows each window and its reset for the signed-in account. For more than one account, or for Claude and Codex together, AI Cooldown shows every window with a countdown on one page, read from Anthropic's own usage endpoint. Terminal monitors that parse your local logs can add token counts and cost estimates, at the price of being estimates.

Inside Claude Code

Type /usage. It shows the session window, the weekly window and any per-model windows, each as a percentage with the reset time. This is the source of truth for the account you are signed into, and it is free. The limitation is that it is one account, in one terminal, when you remember to ask.

On claude.ai

The account settings show the same windows for the signed-in account. Same limitation: one account at a time, and you have to go and look.

Terminal monitors that read local logs

Tools such as Claude Code Usage Monitor watch the JSONL logs Claude Code writes under your home directory and add up tokens per session, then estimate cost and predict when you will hit a limit. They are useful for seeing how many tokens a session actually took and what it would have cost on the API. The trade-off is that the limits themselves are inferred, not read, so the percentages can disagree with what Anthropic reports, and they only see the machine they run on.

AI Cooldown

AI Cooldown reads the same official usage endpoint the CLI uses, for every Claude and Codex account you connect, and shows the result on one page: each window with a countdown to its reset, the one that is currently limiting you flagged, a Go or Wait verdict per provider, the accounts ranked by headroom, and a timeline of every upcoming reset. It also keeps a 48-hour history in your browser to show your burn rate and whether you will run dry before the reset.

Connect an account by signing in through the normal Claude login, or by pasting the token Claude Code already saved in ~/.claude/.credentials.json. It reads limits and your account email, nothing else. The code is open source and you can run it yourself if you would rather not use the hosted version.

Which one to use

One account, occasional check: /usage.
Several accounts, or Claude and Codex together, and you want to know which to use right now: AI Cooldown.
You want token counts and API-equivalent cost per session on your own machine: a local log monitor, alongside either of the above.

see your exact numbers

Want the exact reset for your accounts?

Connect your Claude and Codex accounts to AI Cooldown and get every window with a live countdown, which one is limiting you, and which account to use next. Free, open source, and it reads the same official usage endpoints the CLIs use.

Connect an account

Questions people ask

Is there a built-in way to see Claude Code usage?: Yes, the /usage command shows each window and its reset time for the signed-in account.
Can I track usage across several Claude accounts?: The built-in tools show one account at a time. AI Cooldown shows all of them side by side, with Codex accounts too.
Does AI Cooldown see my conversations?: No. It reads the usage endpoint, which returns percentages, reset times and the account email. Signed-in tokens are encrypted at rest and never sent back to the browser; without signing in they stay in your browser.