How to Check Claude Code Token Count (and Stay in the Flow)

March 30, 2026

To check your Claude Code token count, run /usage in any Claude Code session. This shows your current usage against the active window's limit. For a persistent, always-visible view, Usagebar sits in your macOS menu bar and updates in real time, no terminal context switching required. It alerts you at 50%, 75%, and 90% thresholds so you never hit a 5-hour lockout mid-PR.

Built-in method: /usage slash command inside Claude Code
Web method: claude.ai/settings/usage dashboard
Menu bar method: Usagebar (macOS, free for students)
Usage windows reset on a rolling 5-hour basis, not midnight

What does "token count" mean in Claude Code?

Claude Code measures consumption in tokens, the fundamental unit Claude uses to process both your instructions and its own responses. Every file you load into context, every prompt you send, and every line of code Claude generates counts toward your plan's token budget for the current usage window.

Claude Pro and Max plans both include Claude Code access, but with different limits. According to Anthropic's support documentation, heavy Claude Code usage counts against the same usage pool as your regular Claude conversations. Burning through tokens on a large refactor can leave you rate-limited at the worst possible moment.

How to check token count with the /usage command

The fastest way to check your Claude Code token count is the built-in slash command. Open any Claude Code session in your terminal and type:

/usage

Claude Code will return a summary of your usage for the current window, including how much of your limit you have consumed. This is the native, zero-setup method available to all users.

The limitation is that it requires an active session context. You have to switch to your terminal, open (or resume) a Claude Code session, and run the command. For developers who live across multiple workspaces and IDE windows, that context switch adds friction. More importantly, it gives you a snapshot, not a live feed.

Claude Code includes several slash commands for managing sessions, including /clear to reset context length and /compact to summarize and compress long conversations, both of which directly affect token consumption.

How to check token usage on the Claude web dashboard

If you prefer a browser-based view, navigate to claude.ai/settings/usage. This page shows your usage history across all Claude products, including Claude Code sessions. It breaks down consumption by time period and lets you see patterns across multiple windows.

The web dashboard is useful for retrospective analysis: understanding which sessions were token-heavy, identifying when your window typically resets, and auditing usage for billing purposes. It is not useful for in-the-moment awareness during a coding session.

Why real-time visibility matters: the 5-hour lockout problem

Claude Code usage operates on a rolling window, not a fixed daily reset. When you hit the limit, you are locked out for up to 5 hours. If that happens at hour three of debugging a complex bug or right before you need to wrap up a PR review, you have no fallback.

The /usage command tells you where you are only when you remember to ask. Most developers do not check it regularly enough to catch the cliff before they fall off it.

This is the core problem Usagebar solves: passive, ambient awareness without any action required from you.

How Usagebar shows your Claude Code token count in the menu bar

Usagebar is a lightweight macOS menu bar app that connects to your Claude account and displays your current usage percentage at a glance, right next to your clock. No terminal. No browser tab. No context switch.

Key features relevant to token count tracking:

Live usage percentage: Visible in the menu bar at all times during a session
Smart threshold alerts: Notifications fire at 50%, 75%, and 90% of your limit, giving you time to save work, finish the current task, or plan around the reset
Reset time countdown: Shows exactly when your usage window resets so you can plan accordingly, not just guess based on when you started
Secure credential handling: Your API credentials are stored in macOS Keychain, not in a config file or plaintext
Pay what you want: Flexible pricing with a free option for students

The 90% alert is particularly practical. It gives you a clear signal to wrap up the current task, push your changes, and move to lighter work before the window closes. That single notification can be the difference between a clean handoff and a 5-hour wait with uncommitted changes.

Comparing methods: /usage vs. web dashboard vs. Usagebar

Method	Real-time	Requires action	Alerts	Reset info	Platform
`/usage` command	Snapshot only	Yes (open session)	No	No	All
claude.ai/settings/usage	Near real-time	Yes (open browser)	No	Partial	All
Usagebar	Live	No (always visible)	Yes (50/75/90%)	Yes (countdown)	macOS

Tips for reducing token count during a Claude Code session

Knowing your count is the first step. Controlling it is the second. A few practical habits keep sessions leaner:

Use /clear to reset context between unrelated tasks. Carrying a full conversation history into a new problem burns tokens on context Claude does not need.
Use /compact when a session grows long. This summarizes the conversation into a compressed form, preserving the essential context while freeing up token headroom.
Be specific with file references. Loading entire directories when you only need one function is a common source of unnecessary token spend.
Break large tasks into smaller, focused sessions rather than one marathon prompt chain.

For a deeper breakdown of strategies, see the guide on how to reduce Claude Code token usage and the Claude Code token usage calculator for estimating consumption before you start.

When does the Claude Code usage window reset?

Claude Code usage resets on a rolling 5-hour window from your first message in that session. It does not reset at midnight or on a fixed schedule. This means the reset time changes every day depending on when you start working.

Usagebar surfaces the exact reset time as a countdown, which means you always know whether you have 4 hours left or 20 minutes. Without this, most developers guess, and frequently guess wrong. For more detail, see when does Claude Code usage reset.

Key takeaways

Run /usage inside Claude Code for an immediate snapshot of your token count
Visit claude.ai/settings/usage for historical data and billing context
Use /compact and /clear to manage token spend within a session
For passive, real-time tracking without context switching, Usagebar displays your usage in the macOS menu bar with threshold alerts at 50%, 75%, and 90%
Plan around the 5-hour rolling reset window, not a fixed daily schedule

If you are on macOS and regularly push Claude Code sessions to their limits, Get Usagebar for instant download with flexible pricing, including a free tier for students.

Sources

Track Your Claude Code Usage

Never hit your usage limits unexpectedly. Usagebar lives in your menu bar and shows your 5-hour and weekly limits at a glance.

Get Usagebar