Type /usage inside any Claude Code session to get an instant snapshot of your current token consumption, remaining allowance, and when your usage window resets. It's the fastest built-in way to check where you stand, though it only shows data for the active session window. For persistent, always-visible stats without switching context, developers on macOS pair it with Usagebar.

  • Works on Claude Pro and Max plans via the Claude Code CLI
  • Shows tokens used, remaining budget, and reset timer
  • Usage windows are rolling 5-hour blocks, not calendar-day resets

What does the /usage command show in Claude Code?

The /usage slash command is part of Claude Code's built-in slash command set. When you run it inside an active Claude Code session, it returns a summary of your token usage for the current billing window, including:

  • Tokens consumed so far in the current session
  • Your plan's limit threshold
  • Approximate time until the usage window resets

According to Anthropic's support docs on using Claude Code with Pro or Max, usage is measured in 5-hour rolling windows rather than a fixed daily quota. That distinction matters: hitting the cap at 11pm doesn't mean you're free again at midnight.

How to run /usage step by step

Using the command requires no setup. It's available the moment you have an active Claude Code session running.

  1. Open your terminal and start a Claude Code session with claude
  2. At the prompt, type /usage and press Enter
  3. Claude Code returns your current token stats inline, without interrupting your workflow
  4. Resume your task immediately after reviewing the output

You can also check usage outside the CLI by visiting claude.ai/settings/usage, which shows a broader history across all Claude surfaces, not just Claude Code sessions.

What the output actually means

The numbers /usage returns can be confusing the first time. Here's how to read them:

Field What it means Why it matters
Tokens used Input + output tokens consumed this window Tracks burn rate against your plan ceiling
Remaining Tokens left before rate limiting kicks in Tells you if you can finish the current task
Reset in Time until the 5-hour window rolls over Critical for planning when to start large refactors

The practical risk here is committing to a large task, like a multi-file refactor or wrapping up a PR, only to get rate-limited halfway through. Anthropic's usage limit best practices page recommends checking your remaining quota before starting any high-token operation for exactly this reason.

Limitations of /usage you should know

The built-in command works, but it has gaps that matter for daily development:

  • Session-only scope: It reports on the current CLI session. If you've run multiple sessions across the same window, the aggregate picture isn't always clear.
  • No alerts:/usage is reactive. You have to remember to run it. There are no proactive notifications when you're approaching the 50%, 75%, or 90% threshold.
  • Context switching: Checking usage means stopping your current task, typing the command, reading output, then resuming. It breaks flow.
  • No reset countdown in the background: Once you close the session, you lose visibility on when the window resets unless you go to the web dashboard.

For a deeper breakdown of what the limits actually are across plans, see how Claude Code usage affects Pro limits and the difference between the weekly limit and the 5-hour lockout.

Getting real-time usage stats without interrupting your flow

If you're hitting /usage frequently, that's a signal you'd benefit from persistent visibility. Usagebar sits in your macOS menu bar and shows your Claude Code usage at a glance, without requiring you to context-switch into the terminal.

Key features that go beyond what /usage provides:

  • Live usage bar: Visual indicator of consumption updated continuously, visible from any app
  • Smart alerts at 50%, 75%, and 90%: Get notified before you hit the wall, not after
  • Reset timer in the menu bar: Always know exactly when your 5-hour window resets, so you can time large tasks accordingly
  • Secure credential storage: Uses macOS Keychain, credentials never leave your machine
  • Pay what you want: Free for students, flexible pricing for everyone else

The 5-hour lockout is frustrating precisely when it happens at the worst moment: mid-PR, mid-refactor, or mid-debugging session. Knowing you're at 75% with 40 minutes left in the window changes how you prioritize the next task. That's what persistent visibility gives you.

Other ways to check Claude Code usage statistics

Beyond /usage, there are a few other routes to the same information:

  • claude.ai/settings/usage: Web dashboard showing usage history across all Claude surfaces. Good for reviewing trends, not ideal for real-time monitoring during a session.
  • Verbose mode output: Some versions of Claude Code append token counts to the end of each response when run with verbose flags. Check the guide to checking token count per message for specifics.
  • Usagebar menu bar app: Persistent, real-time, with alerts. Covered above.

For understanding the numbers in context, the Claude Code token usage calculator and the explanation of when usage resets are worth bookmarking.

Key takeaways

  1. Run /usage in any active Claude Code session to see tokens used, remaining, and reset time
  2. Usage resets on rolling 5-hour windows, not daily, so plan large tasks with that in mind
  3. The command is reactive: you only see stats when you ask. No alerts, no background monitoring
  4. Check claude.ai/settings/usage for cross-session history
  5. For zero-interruption visibility with proactive alerts, use Usagebar in the macOS menu bar

Sources