Know which assistant is waiting,
and whether you can afford the next task.

The whole picture, on hover

Every meter shows a pace tick — where an even burn would be right now — a projection (“~67% left at reset”, or “Runs out in 2h”), and the reset time as a countdown or an exact time.

The Cost card adds what your local Claude Code sessions would have cost at API list prices: today, yesterday, this week, this month and the last 30 and 90 days, with a 30-day trend, split by model and by project.

A dashboard, so you are not guessing

Press ⌘U for the week in one window: the total first, what you spent each day and on which assistant, the peak day, and every limit on the panel's own meter with how much a day lasts until it resets.

Rest the pointer on a day for its figures, and click days to pin them side by side under the chart. Switch to 30 or 90 days to see the trend, and where the money went by model, in each assistant's colour, and by project, in the accent you chose for the panel. It reads only this Mac account's own figures and sends nothing anywhere.

Every assistant's plan, crossed off as it goes

When an assistant keeps a task list, its row says how far along it is, 2/4, and opens to the list: finished steps crossed off, the one in progress half filled. Claude Code, Codex, Gemini CLI, Kimi Code, GitHub Copilot and OpenCode report theirs through the hook or plugin. Cursor's hooks never report its to-do list, so Notchmeter reads it from the conversation's own transcript instead, with nothing to set up.

A step that's blocked gets a mark of its own, and a cancelled step stays on the list, crossed out in grey and left out of the count. The row also shows the model the session runs on, written the way you'd say it (GPT-5.5, Opus 4.7), and a Compacting mark while the assistant summarises its context, wherever it reports either.

The hook is optional. Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot CLI and Kimi Code each have one, and OpenCode has a plugin; with it, the notch refreshes the moment a turn ends and knows each session's state as it changes. Without one, the sessions running in your terminals are still listed, each marked as found without it.

Cursor, answered from the notch

Cursor works differently from the other assistants. Its hooks report no task list, no plan and no event that says it is waiting for you, so Notchmeter reads the rest from Cursor itself. A plan appears on its chat's row when Cursor creates it, before it is built, with its to-dos, View Plan and Build, and the turn that builds it is named for the plan.

Two switches on Cursor's page in Settings, both off until you turn them on, let you answer it. Require notch approval for every command holds each shell command and MCP call for Allow or Deny in the notch; one nobody answers goes back to Cursor's own prompt, so nothing is allowed for you unanswered. Mirror Cursor's cards opens the notch on Cursor's own Run prompt and its switch-to-Plan-Mode card, in Cursor's words, and presses the button you pick in Cursor. A question Cursor asks is answered there too: pick a choice and press Continue, as in Cursor. One asked while Cursor's window is minimised or hidden still reaches the notch, shown with a button that brings Cursor back to answer it. A chat whose commands keep failing says May be stuck.

The mirror reads Cursor's windows through the Accessibility permission, never the screen, while a Cursor chat is in a turn and when you press Build. While it is on, Cursor's editor shows Screen Reader Optimized unless you turn that off in Cursor's settings.

Read a plan without leaving the notch

View Plan shows a Cursor plan on its chat's row: its name and the summary Cursor wrote for it, or the plan's first paragraph where it wrote none, read from the plan file when you open it and kept only while it is open. Open in Cursor under it takes you to the plan itself and closes the notch, and Build sits beside it while the plan is ready to build.

With Show what a session is working on off, or with Hide usage while the screen is shared or recorded on while it is, a plan's words stay out of the notch and View Plan goes straight to Cursor.

It says when an assistant wants you

When Claude Code stops for a permission prompt or a question, the rings take the blue that means needs you, not running out, and a white dot says which readout it is — with a count when more than one session is waiting. A turn ending gets the same blue and a tick, for ninety seconds, on every ring with a hook. Claude Code, Codex, Gemini CLI, Copilot and OpenCode report a wait, because each documents an event that means the agent is asking you. Kimi Code documents none, so its ring never claims one. Cursor has no hook event for a wait either, so its ring shows the tick, and a turn gone quiet for 45 seconds with nothing running as a wait worded may be, rather than claiming one it cannot see; with either of Cursor's two switches on, a held command or one of Cursor's own cards is a wait it can see, and says so.

Colour is never the only carrier. The dot and the tick stay if you turn the colour off, the cap on a ring's end keeps saying a window is nearly gone, and every readout has a VoiceOver label.

And you answer it there

When Claude Code stops for a permission, the panel opens on that request and nothing else: what the tool wants to do, an excerpt of it, and Deny or Allow under your thumb. When it asks a multiple-choice question, you pick the answer the same way. Then the panel closes again and the turn carries on, without a window ever taking your place in the terminal.

Codex and GitHub Copilot CLI answer permission requests the same way, and the card says which of them is asking. Every part of it fails open: hand it back with Answer in the terminal or Escape, let the hold run out, switch it off in Settings, or quit Notchmeter altogether, and the terminal asks exactly as it always has. The card shows what a tool wants to do, never your prompt or the file it is editing.

Cursor is answered there too. With Mirror Cursor's cards on, its own Run prompt and its switch-to-Plan-Mode card open the notch with Cursor's buttons, and a question it asks opens with its choices: pick one, press Continue, and Cursor carries on with your answer. A question asked while Cursor's window is minimised or hidden still reaches the notch, shown with a button that brings Cursor back to answer it.

Notch, or any edge you like

No notch, or you'd rather it lived elsewhere? The left and right edges cut the same notch shape into the side of the screen and open the panel beside it, with the readings still on the glass. There's a bar above the Dock too, and a pill under the menu bar on a notchless Mac.

Beside the notch, the strip fits itself to the room the menu bar actually leaves: it moves aside as the frontmost app's menus grow, and only once both ends have closed in does it drop to plain rings.

Go full screen and it gets out of the way. Not for everything, though: name the apps you want the meters beside, a call or a screen share, and they stay. One shortcut flips it for whatever is full screen right now, which is what you need when a film and a meeting are the same browser window.