How to Monitor Claude Code on Your Mac (2026)

#The signals Claude Code gives you

Before you pick a tool, it helps to know what Claude Code actually emits, because every monitor on this page reads one of two things. First, Claude Code writes a running JSONL transcript of each session under your home folder at ~/.claude: prompts, tool calls, token counts and timestamps all land there as plain text you can tail. Second, it exposes lifecycle hooks, small shell commands you register in settings that fire on events like a notification, a finished response, or a tool call waiting for your approval.

A tracker either reads those log files to compute how much of your window you have burned, or listens for a hook to know the exact moment an agent stops and wants you back. Neither path touches the Anthropic API or your account; it is all local files and local events. That single fact is why this whole category exists and why most of it is free. If you want the wider notch context first, the Dynamic Island for Mac guide maps the surface these tools draw on.

#Native notifications with Claude Code hooks

The cheapest monitor ships with Claude Code itself. Hooks let you attach a command to an event, and the two most useful events are Notification (Claude wants input or approval) and Stop (the agent finished its turn). Wire either to osascript and you get a real Notification Center banner without installing anything:

// ~/.claude/settings.json
{
  "hooks": {
    "Notification": [
      { "hooks": [
        { "type": "command",
          "command": "osascript -e 'display notification \"Claude needs you\" with title \"Claude Code\" sound name \"Glass\"'" }
      ]}
    ]
  }
}

Swap in terminal-notifier if you want a clickable banner that raises the right terminal, or pipe the event JSON into a script that decides what to say. The exact hook schema evolves between releases, so check Anthropic's current hooks documentation before you copy a config verbatim. This path is perfect when you run one agent at a time and just want to know when to look back. It does not give you a persistent readout of usage or a live status you can glance at; for that you want one of the always-on tools below.

#Menu-bar trackers that read your logs

A growing shelf of small utilities parks a live indicator in the macOS menu bar and updates it from the same ~/.claude data. They are mostly free and open source, and the names you will run into include:

• ClaudeBar, ClaudeUsageBar and ClaudeMeter: usage-first readouts of tokens and your rolling plan window.
• Claude Status and Claude Code Notifier: session-state and alert-first, showing whether an agent is working, waiting, or done.
• claude-notify, claude-monitor and claude-status-bar: variations on the same idea, each with its own take on layout and alerting.

I have not run every one of these, and I would not pretend to; the category moves quickly and projects vary in polish and upkeep. The shared strength is that a menu-bar tracker sits out of the way and answers one question at a glance: how much have I used, and is anything waiting on me. The shared limit is real estate. A menu-bar item is a tiny slot of text, so it shows a number or a dot, not a rich status. Check each project's repository for what it reads and how actively it is maintained before you lean on it.

#The notch approach: VibeIsland and NotchBay

The other place to put status is the notch, the strip of screen above your windows that is always visible and sits dead center in your eyeline. Two apps use it very differently, and the difference matters.

VibeIsland (vibeisland.app) is the specialist. It bills itself as a Dynamic Island for your AI coding agents, and it means it: you can monitor, approve and answer up to 26 agents (Claude Code, Codex, Gemini CLI, Cursor and others) from the notch without switching windows, jump precisely into any of 20-plus terminals including split panes, review a plan rendered as Markdown, and hear 8-bit sound alerts when an agent needs you. It tracks usage quotas for Claude and Codex, can watch sessions over SSH, and runs fully local under about 100MB of RAM on Apple Silicon. It is $19.99 one-time for one to three Mac licenses with a year of updates, and it keeps working after that. If your day is running many coding agents at once, this is the purpose-built tool. I go deeper on that whole idea in Dynamic Island for AI agents.

NotchBay, the app I build, comes at it from the other end. It is a general notch suite (music, calendar with one-tap join, Zoom and Meet call controls, an OCR clipboard tray, on-device dictation, drop-to-share, AirPods, a privacy chip) that also surfaces developer signals: your Claude plan usage, both the 5-hour and weekly limits, read locally from the ~/.claude logs with no account or API, plus a running background-agent status in its ambient layer. The honest limit: NotchBay glances Claude usage and one agent's status. It does not orchestrate 26 agents, approve tool calls, or jump between terminals. If you want a full notch suite that also keeps an eye on Claude usage, that is NotchBay; if agent orchestration is the job, VibeIsland is built for it. The VibeIsland vs NotchBay comparison lays the two side by side.

#Which monitor fits your setup

Match the tool to how you actually work, not to the longest feature list:

Pricing and features move; confirm current details on each app's own site.

Rules of thumb from testing all four styles: if you run a single agent and want zero new software, wire a hook. If you want a passive usage number and nothing else, a menu-bar tracker is the lightest pick. If you juggle several agents and terminals and want to approve them without context-switching, VibeIsland is the specialist. And if a Claude usage glance is one of many things you want the notch doing, NotchBay folds it into the suite. However you choose to monitor Claude Code on Mac, the signals stay on your machine, so the decision is about surface and depth, not about privacy. NotchBay needs macOS Tahoe (26) for on-device dictation and ships a 3-day trial; the exact notch it draws into is measured to the point in the notch size post.

#Frequently asked questions