Works with
Gemini CLI monitor for Mac, in your notch
CrewTower is a Gemini CLI monitor for Mac that lives in your notch: what each session is doing, how long it has been at it, and which one is waiting on you, brought forward the moment it stops. When it stops for your approval, the card shows the call and Jump takes you to the prompt.
A session you do not have to keep in view
A CLI agent is only as unattended as your willingness to keep checking on it. In practice that means a terminal window you leave uncovered on a corner of the display, or a habit of tabbing over every few minutes to see whether anything has happened yet.
CrewTower replaces both. The session lives in the notch, at natural size, doing nothing until there is something to say. When the agent needs you, its card comes forward with the exact call on it.
The call, not the raw JSON
Tool inputs are parsed once when they arrive, and the notch renders that typed shape rather than a blob of JSON. You see the file, the command, the parameters that matter.
A tool with no bespoke card falls back to a generic one carrying the flattened parameter list, so an unfamiliar call still shows what it will do. Destructive shell commands are flagged on the card.
Answered in Gemini CLI, brought forward by the notch
Gemini CLI asks for approval in its own prompt and acts only on the answer given there, so CrewTower does not try to answer it from the notch. Its hooks only watch: they never hold a tool call, so Gemini CLI never waits on the notch.
When Gemini CLI shows its approval prompt, the session's card comes forward with the call on it and says where to answer. One press of Jump lands on the prompt; nothing is typed for you.
What CrewTower can do for a given session depends on what that agent exposes. Claude Code, Codex, Cursor, Qwen Code and opencode are answered from the notch; for Gemini CLI the notch is where you see the request, and its own prompt is where you answer it.
Land on the exact tab
Jump focuses the place a session belongs to: the exact tab in Terminal, iTerm2 (down to the split) and Ghostty; the pane in WezTerm, tmux, herdr and the Herdr app, and in kitty with its remote control on; Warp's tab through the focus link Warp provides; and the window in Alacritty, which has no tabs. A terminal with no built-in support can be taught with one line containing placeholders, and a custom rule always beats the built-in one. How Jump finds the exact tab is written up terminal by terminal.
macOS Accessibility permission is used for Jump in the terminals that need it, such as Ghostty and Alacritty, and to tell whether you are already looking at a session. Seeing a session in the notch does not.
Setup is one launch
Hooks are configured the first time CrewTower runs, and cleaned up when you remove the app.
# nothing to run. Open CrewTower once, then start Gemini CLI
# the way you always do:
geminiNothing leaves the Mac
Sessions are read from what the agent already writes locally, and hook events travel over a local socket. There are no accounts, nothing to log into, and no analytics in the app. Transcripts, prompts and diffs never leave the machine, and no session is visible from another one.
Where it fits
CrewTower is a status surface for the Gemini CLI sessions you started yourself, in whichever terminal you already use. It shows how much context each session has left, and its usage meter shows how much of your Claude Code or Codex subscription window is left.
Questions
Does CrewTower work with Gemini CLI?
Yes. Gemini CLI is one of the agents CrewTower speaks to natively: live status for every session, and the card comes forward when Gemini CLI asks you to approve a tool call. You answer in Gemini CLI itself, one press away with Jump.
Do I need to write a Gemini CLI config file to use CrewTower?
No. Hooks are configured on first launch and removed again when you delete the app. There is nothing to edit by hand and nothing left behind.
Does Gemini CLI support hooks?
Yes. Gemini CLI reads hooks from its settings.json, by default in ~/.gemini. CrewTower adds hooks there on first launch that only watch: they tell the notch what each session is doing and when Gemini CLI shows its approval prompt, and never hold a tool call.
Does it work if I have several sessions open?
Yes. Each gets its own card, and the ones waiting on a human sort to the front.
What happens with a tool CrewTower has no card for?
It falls back to a generic card carrying the flattened parameter list, so the notch still shows what the call will do.
Does it show token usage?
As context: it shows how much context each Gemini CLI session has left, and its usage meter covers the Claude Code and Codex subscription windows.
Does CrewTower send anything to Google or to a server?
Nothing about your sessions. CrewTower is local-first: sessions are read from what the agent already writes on your Mac, hook events travel over a local Unix socket, and the app has no accounts and no analytics. The only network requests the app makes are the optional usage meter, the free trial and license activation, and update checks, and the privacy page lists all three.
Does it work with other agents too?
Yes. Claude Code, Codex, Cursor, Qwen Code and opencode are spoken natively. The twenty other agents CrewTower recognises get a card you can jump from, and the agents page lists all twenty-six with what it does for each.
Stop checking terminals
One price, one Mac, no subscription. Explore the interactive demo on our homepage, then try the Mac app on your own sessions.
Get CrewTower for MacFree for 3 days, no card · then $9.99 once · macOS 15 or later