How do you know when Claude Code is waiting on you?
I run two or three coding agents most days, each in its own terminal, each in a different project. They stop whenever they need permission to run a command or edit a file, and I'd find out twenty minutes later.
So Vitals 1.12 puts the request in the MacBook notch: the agent, the project, the command, and Allow, Always Allow, or Deny. It works with Claude Code and Codex. Gemini CLI shows up there too, but only its own terminal can say yes.

What comes with it:
Every project has its own colour, so with three sessions waiting, you allow the right one.
When Claude Code asks a question, the choices show in the notch, and one click answers it.
A turn that took 30 seconds or more ends with a line saying how long it took and which dev servers it left running.
Alerts that need you to come out of the notch too, like the Mac running out of memory, with Quit beside the app using the most.
On a Mac without a notch, it all comes down from Vitals in the menu bar. Vitals keeps none of your prompts and sends nothing anywhere.
Vitals is an Activity Monitor alternative for Mac, $19 once during the launch (regular price $49): vitalsmac.com
How do you keep up with agents waiting on you today? And which agent should it work with next?


Replies
the per-project colour is a smart touch, since clicking Allow on the wrong session is the real risk with three waiting. does Always Allow stay scoped to one project or carry across all of them?
@neerajnathany Thanks. Always Allow keeps the rule the agent itself offers, so the scope is the agent's, not Vitals'. With Claude Code that is usually this session or this project, and rarely every project. Vitals says which under the request before you click, for example "Always Allow keeps "npm test" allowed in this project." So allowing it in one project's session doesn't allow it in the other two.
Finding out twenty minutes later is the real cost. Putting the request where your eyes already are is smart. Does it show what the command will touch, or only the command? Half the time I'd say yes faster if I could see which files it's about to change.
@geekynaman Thanks. For a file edit it shows the file's path and how many lines it adds and removes, for example src/cart/Checkout.tsx +5 −3. A Codex patch that changes several files lists each one. For a shell command it shows the command itself, since a command doesn't say up front which files it will change. A long command can be opened in full with Show All before you allow it.
@attacomsian That's exactly what I'd want to see before saying yes. The +5 −3 per file is enough to judge most edits at a glance, and Show All covers the case where the command itself is the risk. Nice work on this.
Cool! The same thing happens with people, just more slowly. A client email waiting on a yes from you sits there just as quietly as a stuck agent. Would you ever extend the notch to things like a calendar invite that still needs an answer?
@abhishek_nellikkalaya Thanks. Probably not. The notch is for what's running on your Mac: agents waiting on you, alerts, and apps using too much. Email and calendar invites are a different kind of tool, and your calendar app and Notification Center already handle those.