Home / Guides / Claude Code Usage Trackers
Claude Code Usage Trackers Compared: Choose by Workflow
There is no single best tracker for every job. The right choice depends on whether you need a quick official check, an in-terminal indicator, historical reports, or Mac-wide visibility.
Last updated August 18, 2026 · By Soren Starck
Answer first
- Check now, no install: Claude Code's built-in
/usage. - Keep 5-hour and 7-day limits in view while you work: Claude Code's official custom status line, free and documented for Pro and Max.
- Report across several agent CLIs: ccusage, which documents 16 supported CLIs plus JSON output.
- Monitor Claude closely in a terminal, with exports: Claude-Code-Usage-Monitor (CCUM), which labels official values against its own estimates.
- See usage outside the terminal on a Mac: a native menu-bar app such as SessionWatcher, our own product, which is macOS-only and paid.
- Reconcile a bill: your account's own billing view, not a locally estimated session cost.
Source policy: every capability claim below is attributed to a primary source and was checked on August 11, 2026, Anthropic's own documentation for Claude Code, and each project's own README for ccusage and Claude-Code-Usage-Monitor. “Not documented” means the cited source did not state the capability on that date; it does not prove the capability is absent. SessionWatcher is our own product, so its entries are marked as first-party. Capability claims are checked against the shipping app source rather than against marketing copy, and the tool-coverage count was re-verified August 18, 2026.
What each number means
Usage tools can put different numbers next to a percent sign or dollar sign. Treating them as interchangeable leads to bad decisions. Four different numbers are in play, each with its own source:
Plan limit used, and reset time
Source: Anthropic, from your subscription. Five-hour and seven-day windows. Availability depends on plan and account type.
Session tokens and context
Source: the current Claude Code session, on this machine. Context fullness is not a plan limit.
Estimated cost
Source: computed locally from token counts at list rates. An estimate, not a charge.
Authoritative billing
Source: your account's own billing view, such as the Claude Console for API usage. This is the figure that settles what you actually pay.
- Plan-limit usage: the share consumed in a five-hour or seven-day subscription window. Anthropic's status-line documentation defines
rate_limits.five_hour.used_percentage,rate_limits.seven_day.used_percentage, and matchingresets_attimestamps. It documents those fields as appearing only for Claude.ai Pro and Max subscribers after the first API response in a session, with each window independently able to be absent. Limits themselves vary by plan and account. - Context-window usage: how full the current conversation context is. It is not a subscription rate limit, and a context or auto-compact warning is not a usage-limit warning. See our Claude Code rate-limits guide for the distinction.
- Tokens and recorded activity: local session records can be aggregated into daily, monthly, model, or project reports. These describe activity recorded on that machine. Anthropic notes the same limitation for the
/usagebreakdown: the figures are approximate and computed from local session history, so usage from other devices or from claude.ai is not included. - Estimated session cost: Anthropic says Claude Code computes this dollar figure locally from token counts priced at standard list rates, so it does not reflect promotional pricing or contracted discounts and may differ from your actual bill. Anthropic also states the session cost is not relevant for billing purposes on Max and Pro subscriptions, where usage is included in the plan. See the Anthropic cost documentation.
- Authoritative billing: for API-billed usage, Anthropic points to the Claude Console Usage page. Subscription, Team, and Enterprise accounts follow different documented paths, so check the cost documentation for the one that matches your account.
Choose by task
Each workflow below states the setup it needs and links to the primary source the capability was read from, so you can re-check it against a newer version yourself.
1. I use one Claude session and need to check now
Run Claude Code's built-in /usage. Anthropic documents a Session block with token statistics and a locally computed dollar figure, intended for API users. On a Pro, Max, Team, or Enterprise plan the same screen documents plan usage bars, activity stats, and a usage breakdown, with d and w switching between the last 24 hours and the last 7 days. Anthropic also documents what happens when the plan-limit request fails: /usage shows the last usage bars loaded on that machine within the past 60 minutes, labeled as last-known usage, and r retries.
Setup: none beyond Claude Code itself. Source: Anthropic, Manage costs effectively (checked August 11, 2026). Our own walkthrough: how to check Claude Code usage.
2. I use Pro or Max and want 5-hour and 7-day limits beside the terminal
Claude Code's custom status line runs a local script and receives JSON session data on stdin. Anthropic documents fields for context-window usage, an estimated session cost in cost.total_cost_usd, and rate_limits percentages and reset timestamps for the five-hour and seven-day windows. The documentation limits those rate-limit fields to Claude.ai Pro and Max subscribers after the first API response in the session, and each window can be absent, so a script should handle missing values. This is free and official, but it is visible only while Claude Code is open, and the script is yours to maintain.
Setup: run /statusline and describe what you want, or add a statusLine command to settings.json and make the script executable. Source: Anthropic, Customize your status line (checked August 11, 2026).
3. I switch between Claude, Codex, and Gemini and want daily or monthly reports
ccusage reads local CLI usage data and prints reports. Its README documents unified reporting across 16 agent CLIs, including Claude Code, Codex, OpenCode, Copilot, Gemini, Kimi, and Grok, plus a Claude five-hour block report with active monitoring, JSON output, and a beta Claude Code status-line integration. That combination fits when reporting across several local CLI data sources matters more than a graphical interface. Because it reads local data, its reports cover what those CLIs recorded on that machine.
Setup: a terminal, using the install and report commands in the README. Source: ccusage README (checked August 11, 2026; latest release observed v20.0.19, July 27, 2026). Capability claims here are version-sensitive.
4. I want a Claude-focused live terminal monitor with forecasts and exports
Claude-Code-Usage-Monitor (CCUM) is the closer fit here. Its README documents a live terminal UI, capture of official status-line rate_limits values, labeled local estimates when official values are not fresh, forecasts, state and JSON and CSV output, and an optional local history store. It is Claude-focused rather than multi-agent, and it separates official, estimated, and unknown values explicitly, which is useful when you care where a number came from.
Setup: a terminal install, plus a status-line hook if you want the official rate-limit capture rather than local estimates. Source: Claude-Code-Usage-Monitor README (checked August 11, 2026; latest release observed v4.0.0, June 27, 2026). Capability claims here are version-sensitive.
5. I want a Mac-wide glance and a notification, without maintaining a terminal script
The cited sources for the terminal and browser options above do not document this workflow: an indicator that sits at the operating-system level rather than inside a terminal window, and macOS notifications instead of a reading you have to look at. A native menu-bar app is a different workflow, not automatically a better tracker. SessionWatcher is our own product and is described below with that limitation stated plainly.
Setup: a macOS app install; it is macOS-only and paid. Source: our own download page and product pages, which are first-party and were not independently tested for this review.
6. I need bill reconciliation for a team or API account
None of the local tools compared here is the billing authority. For API organizations, Anthropic points to the Claude Console Usage page and workspace-level cost reporting; Team and Enterprise plans have their own admin-side spend reporting; and Pro and Max usage is included in the plan unless usage credits are turned on. Compare a plan charge with a plan-side report, not with a locally estimated session cost.
Setup: account access with the relevant billing or admin permissions. Source: Claude Console Usage and Anthropic's cost documentation (checked August 11, 2026). See also how much Claude Code costs.
Comparison matrix
Cells report what the cited source documented on the verification date, not how good a tool is. Rows cover the criteria that actually change the choice: where the number lives, what it covers, what it costs to run, and how much confidence the evidence supports.
| Criterion | /usage | Claude Code status line | Claude Console | ccusage | CCUM | SessionWatcher |
|---|---|---|---|---|---|---|
| Interface and location | Command inside Claude Code | Bar at the bottom of Claude Code | Browser page | Terminal command; beta status line | Live terminal UI; status-line hook | macOS menu bar (first-party claim) |
| Visible when Claude Code is closed | No | No | Yes, in a browser | Yes, when you run it | Yes, while the monitor runs | First-party claim; not independently tested |
| Sources and tools covered | Claude Code, this machine | Claude Code, current session | Anthropic API account | 16 agent CLIs documented, including Claude Code, Codex, OpenCode, Copilot, Gemini, Kimi, Grok | Claude-focused | 15 tools on Pro: Claude Code, Codex, Cursor, Copilot, Gemini CLI, Antigravity, opencode, Devin, Grok, OpenRouter, Z.ai, Kimi, Qwen, DeepSeek, Synthetic (verified against the shipping app source, August 18, 2026) |
| Five-hour usage percentage | Plan usage bars documented on Pro, Max, Team, Enterprise | Documented (rate_limits.five_hour.used_percentage), Pro/Max after first API response | Not documented; Console covers API billing | Five-hour block report with active monitoring documented | Documented from official status-line values, or labeled estimates | First-party claim; not independently tested |
| Reset time | Not documented on the cited page | Documented (resets_at, Unix epoch seconds) | Not documented | Not documented in the source read | Not documented in the source read | Live countdown claimed; not independently tested |
| Seven-day limit | Plan usage bars documented; windows vary by plan | Documented (rate_limits.seven_day), same conditions | Not documented | Not documented in the source read | Not documented in the source read | Not independently tested |
| Proactive OS notifications | Not documented | Not documented | Not documented | Not documented in the source read | Not documented in the source read | Configurable macOS notifications claimed; not independently tested |
| Historical reports | Last 24 hours and last 7 days breakdown documented | Not documented; session-scoped | Yes, account usage reporting | Daily, monthly, session, and block reports documented | Optional local history store documented | Not documented in first-party materials read |
| Export and automation | Not documented | Script receives JSON on stdin; you format the output | Console reporting and admin APIs documented | JSON output documented | State, JSON, and CSV output documented | Not documented in first-party materials read |
| Authoritative for billing | No; cost is computed locally at list rates | No; same local estimate | Yes, for API billing | No; derived from local records | No; derived from local records | No; a local view, not a billing system |
| Platform | Wherever Claude Code runs | Wherever Claude Code runs; Windows setup documented separately | Any browser | Terminal; see project docs | Terminal; see project docs | macOS only |
| Install and maintenance | None | You create and maintain a script | None; account access | Terminal install per README; update for new releases | Terminal install per README; optional status-line hook | App install and updates |
| Data path | Local session history, plus a request to Anthropic for plan limits | Local session JSON to your script | Your account data, in Anthropic's Console | Reads local CLI usage files | Reads local data; optional local store | Local-only handling claimed; not independently tested |
| Price and license | Included with Claude Code | Included with Claude Code | Included; usage billed to the account | Free open-source project; see repository for license | Free open-source project; see repository for license | Paid; see the download page for current terms |
| Evidence type | Anthropic documentation | Anthropic documentation | Anthropic documentation | Project README, version-sensitive | Project README, version-sensitive | First-party product materials; not independently tested |
Matrix sources, all checked August 11, 2026: Anthropic cost docs, Anthropic status-line docs, Claude Console Usage, ccusage README (latest release observed v20.0.19, July 27, 2026), and the Claude-Code-Usage-Monitor README (latest release observed v4.0.0, June 27, 2026). Open-source capabilities can change between releases, so re-check the README before relying on a row. SessionWatcher rows are labeled first-party because we publish this guide. The tool-coverage claim is verified against the shipping product source (Entitlements.proTools in the macOS app), checked August 18, 2026; it is disclosure of an interest, not an admission that the claim is unchecked.
Where we fit
SessionWatcher: best fit for a native macOS workflow
SessionWatcher is our own product, so treat this section as a disclosed first-party description rather than a review. If you prefer a native macOS menu-bar workflow to configuring and keeping a terminal status line open, it is positioned as the paid option for that. It covers 15 tools in a single menu bar - Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, opencode, Devin, Grok, OpenRouter, Z.ai, Kimi, Qwen, DeepSeek and Synthetic - with a persistent reading, a live countdown to reset, configurable macOS notifications, and local handling of your data. That breadth is the honest difference: the free menu-bar trackers in this category are typically built around one tool, so running several agents means running several trackers.
What it is for
One indicator at the operating-system level, outside any single terminal, with notifications instead of a reading you have to go and look at.
Trade-offs
It is macOS-only and paid, while /usage, the official status line, ccusage, and CCUM are free. The capabilities above are first-party claims and were not independently tested for this comparison.
Confirm the current system requirements, supported tools, price, and behavior on the download page before buying. For the narrower native-app versus terminal-reporting question, see SessionWatcher vs ccusage; that comparison is also first-party and is not a substitute for the current ccusage documentation.
Review SessionWatcher for ClaudeFrequently asked questions
Does Claude Code already show plan-limit information?
Yes, in two documented places. On a Pro, Max, Team, or Enterprise plan, Anthropic documents plan usage bars and a usage breakdown on the /usage screen, with a toggle between the last 24 hours and the last 7 days. A custom Claude Code status line can also receive five-hour and seven-day rate-limit percentages and reset timestamps; Anthropic documents those rate_limits fields as appearing only for Claude.ai Pro and Max subscribers, after the first API response in a session, and each window can be independently absent. Checked against Anthropic documentation on August 11, 2026.
Is the cost shown by /usage my Anthropic bill?
No. Anthropic says Claude Code calculates the session dollar figure locally from token counts at standard list rates. It can differ from promotional pricing, contracted discounts, or your actual bill. The Claude Console Usage page is authoritative for API billing; subscription users have usage included in their plan unless they enable additional usage credits.
Can Claude Code show usage in a custom status line?
Yes. Anthropic documents a configurable status line, generated with the /statusline command or configured manually through the statusLine setting. Claude Code sends the script JSON session data documented to include cost.total_cost_usd, context-window fields, and rate_limits fields when they are available. It stays inside Claude Code, and you own the script that chooses and formats the fields.
Does ccusage still cover only Claude Code?
No. The ccusage README, checked on August 11, 2026 with v20.0.19 as the latest release observed, documents unified reports across 16 agent CLIs, including Claude Code, Codex, OpenCode, Copilot, Gemini, Kimi, and Grok. It also documents a Claude five-hour block report with active monitoring and a beta Claude Code status-line integration. These are repository claims read on that date, not product tests, and they can change with later releases.
When does a native macOS tracker make more sense than a terminal status line?
A menu-bar app addresses a different workflow: one indicator at the operating-system level and macOS notifications, rather than a reading that lives inside a specific terminal window or a command you run. A status line is free, official, and always visible while Claude Code is open, so the menu-bar option mainly makes sense if you want visibility when Claude Code is not in front of you and prefer not to maintain a script. SessionWatcher describes menu-bar and notification capabilities in its own first-party materials; those were not independently tested for this review, and it is macOS-only and paid, so confirm the current requirements, price, and behavior before relying on them.