Claude Usage Tracker: 4 Ways to See Your Limits

The official Claude usage tracker is Settings → Usage in claude.ai and Claude Desktop: it shows how much of your 5-hour session and your weekly limit you've used, and when each resets. In Claude Code, /usage shows the same bars, and the status line can keep them on screen while you work. Third-party tools fill two gaps: ccusage turns Claude Code's local logs into token and cost reports, and on a Mac, Clawdrobe shows the limits of several Claude accounts side by side.

This covers Pro, Max and Ultra as of November 2026. Team and Enterprise seats have the same kind of limits, but admins see them in other places.

What there is to track#

Pro, Max and Ultra have two limits running at once: a session limit that resets five hours after the first message of a session, and a weekly limit that resets at a fixed day and time assigned to your account. Some plans also have a separate weekly limit for Fable, and verified Ultra accounts have no session limit. Anthropic says chat, Claude Desktop and Claude Code all draw from the same limits (How do usage and length limits work?). Claude's 5-hour and weekly limits, explained goes through both in detail.

So a useful tracker answers three questions: how much of each limit is used, when each resets, and whether you'll make it to the reset at your current pace.

1. Settings → Usage (built in, every plan)#

Open claude.ai/settings/usage, or Settings → Usage in Claude Desktop. You'll see:

• Current session: percent used and the time until it resets.
• Weekly limits: one bar for all models, plus a Fable bar if your plan has one, each with its next reset.
• Usage credits, if you've turned them on: this month's spend against the limit you set.

It's the most accurate number you can get, because it comes from Anthropic. It only shows the account you're signed in to, and it keeps no history.

2. Claude Code: /usage and the status line#

/usage (also reachable as /cost). For Pro, Max and Ultra subscribers it shows your plan usage bars, activity stats and a breakdown of what counts against your limits. Anthropic's costs page describes that breakdown: recent usage split by skills, subagents, plugins and MCP servers, plus recommendations such as trimming a large CLAUDE.md. Press d or w to switch between the last 24 hours and the last 7 days. The breakdown is approximate and built from session history on that machine, so claude.ai and other machines aren't in it. The dollar figure in the Session block is meant for API users; on a subscription it isn't what you pay.

The status line keeps the numbers in view. Claude Code passes your script JSON on every update, and for Pro, Max and Ultra subscribers it includes rate_limits.five_hour and rate_limits.seven_day, each with used_percentage and resets_at (status line docs). A minimal script:

#!/bin/bash
input=$(cat)
FIVE=$(echo "$input" | jq -r '.rate_limits.five_hour.used_percentage // empty')
WEEK=$(echo "$input" | jq -r '.rate_limits.seven_day.used_percentage // empty')
OUT=""
[ -n "$FIVE" ] && OUT="5h ${FIVE}%"
[ -n "$WEEK" ] && OUT="${OUT:+$OUT · }week ${WEEK}%"
echo "$OUT"

Save it as ~/.claude/statusline.sh, make it executable (it needs jq), and add "statusLine": {"type": "command", "command": "~/.claude/statusline.sh"} to ~/.claude/settings.json. Two things to know: the fields only appear after the session's first response, and either one can be missing or drop out right after it resets (a verified Ultra account has no five-hour window), so the script prints only the parts it has.

3. ccusage (open source, tokens and estimated cost)#

ccusage reads the usage data Claude Code (and other coding CLIs) store on your machine and prints daily, weekly, monthly and per-session reports, plus a blocks view of Claude Code usage grouped into 5-hour windows. Run it with npx ccusage@latest; it's MIT licensed.

It answers a different question from Settings → Usage. ccusage counts tokens and prices them at API rates, so you can see which day or session was heavy and what that work would have cost on the API. It doesn't show the percentage of your plan's limit, because that number only comes from Anthropic, and it only sees coding-tool logs on that machine, not your claude.ai or Claude Desktop chats.

Use it when you want history and trends. Use one of the two options above when you want to know whether you can keep working right now.

4. Several accounts: Clawdrobe#

Everything above tracks one account at a time. If you have a work seat and a personal Pro, or an account per client, Settings → Usage means a sign-in or a browser profile per account, and Claude Code's status line only knows the account that session runs as.

Clawdrobe is a Mac app that gives each of your Claude Desktop accounts its own copy of Claude, and shows every account's 5-hour and weekly usage in one window. For each account it shows:

• both meters and when each resets;
• the weekly pace, how much of the week you've used per day lately, and when the week runs out at that pace;
• across all accounts together, how much weekly room is left and how long it lasts at your combined pace.

It can notify you at 70, 80 or 90% of a limit, and once a week when an account won't last until its reset. If two accounts could do the same job, ⌘ 0 opens the one with the most room left.

Clawdrobe reads these numbers from files Claude Desktop writes on your Mac. It doesn't talk to Claude's servers or read your chats. The catch: Claude only records an account's usage while you're using the Mac, and stops for accounts whose usage menu you haven't opened lately, so a reading for an account you haven't touched in a day can be a day old. Opening the usage menu in that account's Claude updates it.

Clawdrobe is free with every feature for two accounts. Clawdrobe Pro is a one-time $10 for unlimited accounts on up to 3 Macs. It needs macOS 26 or later, runs on Apple silicon and Intel, and isn't affiliated with Anthropic.

Which one should you use?#

A common setup is two: the status line for the account they're coding in, and either Settings → Usage or Clawdrobe for the bigger picture.

Pitfalls#

• Reading the wrong account. Claude Desktop and Claude Code sign in separately, so the app can be on your work account while the terminal is on your personal one. Check /status in Claude Code before trusting its numbers. How to switch Claude accounts in the terminal covers that.
• Treating ccusage's dollars as a bill. On a subscription you pay the plan price; those figures are API prices for the same tokens.
• Assuming a reset that hasn't come. The weekly reset is a fixed time for your account, not seven days from your first message. Check it in Settings → Usage.
• Trusting an old number. A tracker that reads saved data shows the last reading, not now. Before a long task, refresh it.

Quick answers#

• Is there an official Claude usage tracker? Yes: Settings → Usage on claude.ai and in Claude Desktop, and /usage in Claude Code.
• Can I see Claude usage in the terminal all the time? Yes, with a status line script that reads rate_limits.
• Does ccusage show my plan limit percentage? No. It shows tokens and estimated API cost from local Claude Code data.
• Can I see several accounts' usage in one place? Not in Claude itself. On a Mac, Clawdrobe shows them side by side.

If you hit a limit anyway, Claude usage limit reached? What to do next lists your options.