Track your costs
Using the /usage command
The Session block in
/usage shows API token usage and is intended for API users. Claude Max and Pro subscribers have usage included in their subscription, so the session cost figure isn’t relevant for billing purposes. Subscribers see plan usage bars, activity stats, and a usage breakdown on the same screen./usage shows detailed token usage statistics for your current session. Claude Code computes the dollar figure locally from token counts priced at standard list rates, so it doesn’t reflect promotional pricing or contracted discounts and may differ from your actual bill. For authoritative billing, see the Usage page in the Claude Console.
/clear starts a new session, so the next session’s total cost starts at $0. Before v2.1.211, they kept accumulating across /clear for the lifetime of the Claude Code process.
Plan usage breakdown
On a Pro, Max, Team, or Enterprise plan,/usage also shows a breakdown of what counts against your plan limits:
- Attribution: recent usage attributed to skills, subagents, plugins, and individual MCP servers, each shown as a percentage of the total. An MCP server’s share counts only the requests that consumed one of its tool results. Before v2.1.222, after one call to an MCP server, Claude Code attributed every subsequent request to that server, overstating its share.
- Behavior flags: behaviors such as long context or cache misses, flagged when one accounts for 10% or more of recent usage.
d or w to switch between the last 24 hours and the last 7 days. The figures are approximate and computed from local session history on this machine, so usage from other devices or claude.ai is not included.
In the VS Code extension, the same breakdown appears in the Account & usage dialog with a Day and Week toggle. Requires Claude Code v2.1.174 or later.
When the usage request fails
When the request for your plan limits fails, most often because the usage endpoint is rate limited,/usage shows the last usage bars it loaded on this machine within the past 60 minutes, along with a Showing last-known usage note stating how long ago that data was fetched. Press r to retry; a successful retry replaces the last-known bars with fresh data. Without a snapshot from the past 60 minutes, /usage reports that the usage endpoint is rate limited and offers the same retry shortcut. Before v2.1.208, a rate-limited request in a session that hadn’t loaded usage yet always showed the error with no bars.
Analyze your usage patterns
Run/insights for a report on how you work rather than how many tokens you’ve used. It analyzes your recent sessions on this machine and writes an HTML report covering what you work on, friction points such as misunderstood requests or buggy code, and suggestions for using Claude Code more effectively. A single run analyzes up to 200 sessions it hasn’t seen before and skips very short ones. When sessions are left out, the report header shows the analyzed count with the total in parentheses, for example 200 sessions (412 total).
Claude Code writes the latest report to ~/.claude/usage-data/report.html and saves a timestamped copy of each run in the same directory, so earlier reports aren’t overwritten. Claude Code deletes reports on the same schedule as the rest of your session data: at startup, it removes files older than cleanupPeriodDays, 30 days by default.
You can run /insights on any plan and with any provider. The analysis runs through the same provider and account as your regular sessions, and the tokens count against your plan or API usage. Sessions from other devices and claude.ai aren’t included.
Add usage credits to your subscription
Usage credits let you keep working past your plan’s usage limit. To manage them, run/usage-credits after signing in with your claude.ai subscription through /login; the command isn’t available with API key authentication. What it opens depends on your role: