Compared

Claude Code usage monitors for Mac, compared

A Claude Code usage monitor for Mac is one of two tools: a meter that keeps your 5-hour and weekly limit on screen while you work, or a spend report that tells you afterwards what the tokens cost. CrewTower is a meter, in the notch, read from Anthropic's own figure, and it adds the question the others leave out: which of your sessions is waiting for you. Nine are compared below by where the number comes from, what each one keeps and what it runs on.

Every other tool's row is from its own site or repository, checked on 19 October 2026, with prices rechecked on 1 November 2026. Sources.

The two kinds

 Spend reportMeter
AnswersWhat did this cost me?How much have I got left?
When you lookAfterwards, deliberatelyWhile working, without looking
Usually readsYour local session filesYour provider's own record
ShapeA command or a dashboardSomething always on screen
Examplesccusage, CodeBurnCrewTower in the notch; CodexBar and ClaudeBar in the menu bar

Several tools below do both, and the line between them is where the number comes from. A figure rebuilt from local files is accurate about tokens, because the tokens are in the files. It is an estimate of how close you are to being stopped, because your plan's limits live with your provider, and work done on another machine or on claude.ai is not on this disk.

What CrewTower does as a usage monitor

The provider's own figure. ccusage, CodeBurn's spend reports and Claude Code Usage Monitor's default view rebuild usage from local files. CrewTower reads Claude Code's figure from Anthropic's usage endpoint with the login Claude Code already uses, about every five minutes, so it is the provider's own figure rather than a reconstruction; Codex's comes from Codex's own rate limit reporting. CodexBar, ClaudeBar and Claude Usage Tracker read the provider's figure too.

The waiting session, answered. The usage strip is one line under the sessions, worded as each provider words it: Claude as used, Codex as left. The rest of CrewTower shows every running agent session in the notch and brings forward the one that has stopped for you. For Claude Code, Codex, Cursor, Qwen Code and opencode you allow or deny the request from the card; the agent's hook is waiting on a local socket and the answer goes back down it, so the terminal never comes forward. When you do want the terminal, Jump lands on the exact tab or tmux pane.

Context, next to usage. Each card shows how much context the session has left, for the agents that report it, and for Claude Code it suggests compacting at a task break before quality starts to slip.

The usage meter is optional: on by default, switchable off, and one of only three things in the app that make a network request. The privacy page lists all three and names the exact credential and URL.

What Claude Code already shows you

Inside a running Claude Code session, /usage shows the session's cost, your plan usage limits and activity stats; /cost and /stats open the same screen. For history across every session, ccusage reads the transcripts Claude Code already writes under ~/.claude/projects, with no account and no API key:

# inside a Claude Code session /usage # in any terminal npx ccusage@latest daily npx ccusage@latest blocks npx ccusage@latest statusline # for Claude Code's status line (beta)

ccusage's old blocks --live view was removed in its version 18; its docs point to statusline for figures while you work. Between these, most of the question is answered. A separate monitor is worth adding when the problem is that you have to remember to ask.

Nine tools, side by side

 PriceRuns onClaude Code figure fromHistoryA session waiting for you
CrewTower$9.99 once (early bird, regularly $14.99)macOS 15 or later, Apple silicon and IntelAnthropic's usage endpoint, with Claude Code's own login; Codex from its own rate limit reportingNone; with the beta Tell Claude plugin, the current session's cost so farEvery session, for 26 agents; answered from the notch for 6
CodexBarFree, MITmacOS 14 or later; Linux app and command lineClaude's OAuth usage API first, then the CLI or the webRecorded spend by rolling days, month to date or all timeLists live sessions as active or idle; a waiting state is a non-goal
ClaudeBarFree, Apache 2.0macOS 15 or laterclaude /usage or the OAuth usage API30 days; cost estimated at list pricesAn opt-in notch shows “Needs you” for the latest Claude Code session; answering not published
Claude Usage TrackerFree, MITmacOS 14 or laterClaude Code's credentials or a claude.ai sign-inUsage history chartsA beta notch HUD pulses when Claude is waiting; it says it never answers for you
Usage4ClaudeFree, MITmacOS 13 or later; not notarizedClaude's own undocumented usage APIUnder considerationNot published
SessionWatcherFrom $8.99 once; 7-day trialmacOS 14 or later, WindowsThe login already on your computer; some providers' own APIs26 weeks kept; cost estimated from tokensNot published
Claude Code Usage MonitorFree, MITAny system with Python 3.9 or laterA local estimate by default; Claude Code's own figures with --statuslineOpt-in local usage warehouseNot published
ccusageFree, MITAny system, from the command lineLocal session logsDaily, weekly, monthly, session and 5-hour block reportsNot published
CodeBurnFree, MITmacOS, Windows, LinuxLocal session files for spend; codeburn quota asks the providerSpend by tool, model, project and taskNot published

“Not published” means that tool's own pages say nothing about it, not that it cannot. Outside the table, Pulse for Claude Code, a free local dashboard with a notch strip, answers Claude Code's permission prompts through a PreToolUse hook, on its dashboard or a phone through ntfy; CrewTower answers Claude Code and five other agents on the card in the notch.

The rows they win, and what CrewTower does there

Price. Seven of the eight others are free and open source, and SessionWatcher is paid; CrewTower is $9.99 once, and it is the one tool in the table that answers the session waiting for you.

History. CodexBar, ClaudeBar, Claude Usage Tracker, SessionWatcher, ccusage and CodeBurn keep spend or usage over time; CrewTower keeps no history and shows the live window instead, from the provider's own figure.

Providers. CodexBar lists 106, ClaudeBar 28 and SessionWatcher 20 tools; CrewTower's meter covers Claude Code and Codex and sits next to every session of twenty-six agents.

Older Macs. Usage4Claude runs on macOS 13, and CodexBar, Claude Usage Tracker and SessionWatcher on macOS 14; CrewTower is built for macOS 15 and later, on Apple silicon and Intel.

Using more than one

Nothing here conflicts. A common setup is a spend report for the month (ccusage or CodeBurn), a meter for the providers you use (CodexBar or ClaudeBar), and CrewTower for the sessions. If you already keep a meter in the menu bar, CrewTower's own usage strip can be switched off.

Which one to pick

Which session needs me, and answering it without switching windows? CrewTower, with its own meter for Claude Code and Codex, and any meter above beside it if you want more providers.

How much is left, for Claude Code? CrewTower in the notch, /usage inside a session, or a menu bar meter such as Claude Usage Tracker or Usage4Claude.

How much is left, across many providers? CodexBar, or ClaudeBar on macOS 15.

What did I spend? ccusage on the command line, or CodeBurn for a desktop view by project.

Questions

What is the best Claude Code usage monitor?

It depends on the question. For how much of your 5-hour and weekly limit is left while you work, use something always on screen: CrewTower keeps it in the notch from Anthropic's own figure and also shows which session is waiting for you, and CodexBar covers many providers from the menu bar. For what you have spent, by day, session and model, a spend report such as ccusage reads your local logs.

Is there a Claude usage monitor for the Mac menu bar?

CrewTower keeps the window in the notch rather than the menu bar, right above the sessions it belongs to. For the menu bar itself, CodexBar, ClaudeBar, Claude Usage Tracker and Usage4Claude are compared in the table above.

Claude Code Usage Monitor or ccusage?

One is for watching, one for looking back: Claude Code Usage Monitor is a live terminal view of the current window, estimated from local logs unless you feed it Claude Code's own figures with --statusline, and ccusage prints reports of what you spent by day, week, month and session. Many people run both.

How does it decide when to suggest compacting?

It suggests it for Claude Code only, and only at a task break: the turn has ended and Claude is waiting for your next prompt, not stopped on a question. The suggestion comes once the conversation passes about 300k tokens on a 1M window, or 60% of a smaller one (about 120k on 200k), and again after each further 100k. Close to Claude Code's own auto-compact point it says “auto-compact soon” instead.

Sources

Read on 19 October 2026, each from the tool's own site or repository: CodexBar and codexbar.app, with its sessions design notes; ClaudeBar, with its notch notes; Claude Usage Tracker, with its changelog; Usage4Claude; sessionwatcher.com, with its facts page and usage stats page; Claude Code Usage Monitor; ccusage.com, with the live monitoring note, and its repository; CodeBurn; Pulse for Claude Code. Claude Code's commands from its own reference.

All of these are independent projects. Nothing here is a claim about anyone's code; it is what each one publishes, and every cell is checkable in a minute. If a cell is out of date, the tool's own page is the one to trust.

See the window, and the session waiting on you

Explore CrewTower in the interactive website demo, then try the Mac app on your own sessions.

Get CrewTower for Mac

Free for 3 days, no card · then $9.99 once · macOS 15 or later