Back to blog

How to Track Claude Code Usage: The Complete Guide

Learn every method for tracking your Claude Code usage - from built-in commands to CLI tools to full desktop dashboards.

How to Track Claude Code Usage: The Complete Guide

If you are using Claude Code daily, keeping track of your usage is important. Rate limits can interrupt your workflow at the worst time, and without visibility into how much of your allocation you have consumed, you are flying blind.

This guide covers every method available for tracking Claude Code usage, from the simplest built-in commands to dedicated monitoring tools.

The Built-in Options

The /status Command

Claude Code includes a /status command that you can run inside any session. It returns a quick summary of your current rate limit status, showing your utilization percentages for both the 5-hour and 7-day windows.

To use it, type /status at the Claude Code prompt:

> /status

This gives you a snapshot of where you stand. The downside is that you need to be inside an active Claude Code session to check, and it does not provide historical trends or predictions.

The /cost Command

The /cost command shows a summary of token usage and estimated costs for your current session. This is useful for understanding how expensive a particular session is, but it does not show your overall rate limit status or track usage over time.

> /cost

Limitations of Built-in Commands

Both built-in commands are useful for quick checks, but they have limitations:

  • You must be inside an active session to use them
  • No historical data or trends
  • No notifications or alerts
  • No persistent tracking across sessions
  • No visualization of usage patterns

CLI Tools

ccusage

ccusage is an open-source CLI tool that reads your Claude Code session data and provides usage summaries in the terminal. It parses session files to calculate token counts and costs.

To install and run it:

npx ccusage

ccusage is a solid option if you prefer working entirely in the terminal. It gives you more data than the built-in commands, including per-session breakdowns and cost estimates.

However, ccusage is still a terminal tool. You need to remember to run it, and it does not provide real-time monitoring or notifications.

The Desktop Dashboard Approach

For users who want always-on visibility into their Claude Code usage, a desktop application provides the best experience. This is where My Claude comes in.

What My Claude Offers

My Claude is a free, open-source desktop app built specifically for Claude Code monitoring. It runs as a native application on macOS, Windows, and Linux and provides:

Real-time dashboard - See your 5-hour and 7-day utilization percentages updated automatically, without opening a terminal or running any commands.

Historical tracking - Usage data is stored locally so you can see trends over time. Did you use more this week than last? Which days are heaviest? The data is there.

Rate limit alerts - Set threshold notifications at any percentage. Get a desktop notification, WhatsApp message, or Telegram alert when you hit 70%, 85%, or whatever threshold you choose.

Pace predictions - My Claude calculates whether your current usage rate will cause you to hit the limit before the window resets. This is something no CLI tool can do passively.

Per-project tracking - See which projects drive the most usage. Useful if you work across multiple codebases and want to understand where your allocation goes.

System tray - Usage stats visible at a glance from your menu bar or system tray without opening the full app.

Setting It Up

Getting started takes about two minutes:

  1. Download My Claude from the download page
  2. Install and launch it
  3. My Claude automatically detects your Claude Code OAuth token
  4. Your dashboard populates with current usage data

No configuration files to edit, no API keys to paste, no setup scripts to run.

Practical Tips for Tracking Usage

Regardless of which tool you use, here are some practical habits:

Check before long sessions - Before starting a heavy coding session, check your current utilization. If you are already at 60% on the 5-hour window, you might want to pace yourself.

Track weekly patterns - The 7-day window matters more than most people realize. If you burned through 80% of your weekly allocation by Wednesday, the rest of your week will be constrained.

Set alerts proactively - If you use a tool that supports notifications, set them before you need them. A 70% alert gives you enough runway to adjust your approach.

Know your plan limits - Pro and Max plans have different allocations. If you are consistently hitting limits on Pro, the Max plan provides significantly more headroom.

Which Method Should You Use?

MethodBest For
/statusQuick one-off checks during a session
/costUnderstanding individual session costs
ccusageTerminal-native users who want session breakdowns
My ClaudeAlways-on monitoring with alerts and predictions

For casual users, the built-in commands are sufficient. For anyone using Claude Code as a core part of their daily workflow, a persistent monitoring solution saves time and prevents surprises.

Download My Claude to get started with full usage monitoring.