Review the launch plan
Read the request and give your answer, right in the notch.
A LITTLE MORE ROOM TO FOCUS
Keep Claude Code, Codex, and your other AI agents in view. Follow progress and answer requests from your notch, across desktop apps and terminals.
Stay with what you’re doing
A task in Claude. Another in Codex. Something still running in your terminal. CrewTower brings their progress and requests together, so keeping up doesn’t become another task.
Read the request and give your answer, right in the notch.
See that work is moving along without opening the app to check.
Know when it’s ready, then jump back to the right session.
Features
Respond without switching apps. Approve or deny supported requests from the notch. Your answer goes straight back to the session, while your current window stays in focus.
See what you’re approving. Destructive commands get a visible warning, so you can read the request before deciding.
Choose how long approval lasts. Allow once, for this session, or always where the agent supports it. The choice stays yours.
Give an answer and keep going. Pick an option when your agent needs a decision. Questions and choices appear together in the notch.
Read the plan. Have your say. Open the full plan, approve it, or send feedback for a revision. There’s room to review before work begins.
Return to the right session. Jump to a Claude Code or Codex task in its desktop app, or the exact terminal tab or pane for a CLI session.
Know how much context is left. A small ring shows how full each supported session’s context is, with clear warnings as it approaches its limit.
Keep your limits in sight. Check available Claude and Codex usage windows beneath your sessions, so a limit is easier to see coming.
Keep shared screens quiet. Privacy mode holds the panel closed and silences alerts. Your agents keep working in their own apps.
Waiting requests rise above sessions that are still working. The closed notch shows how many need your attention.
A brief announcement lets you know when a task finishes. You can return when you’re ready.
Reminders become less frequent, then stop. Tune sounds by event and keep interruptions on your terms.
See the subagents a session has started and how many have finished, even while the main task is still running.
CrewTower keeps your prompts, files, and transcripts on your machine. No CrewTower account or app analytics.
The notch on your MacBook and a small pill on other displays keep the same familiar controls within reach.
Choose a pixel companion that reacts as your crew works, waits, and finishes. Or keep the bar character-free.
Reopen CrewTower and recover your recent sessions, with their state checked against the latest available activity.
A native Mac app with a small footprint, built to sit quietly at the edge of your screen throughout the day.
Works with
Desktop apps, editors, and terminals. Your crew stays where you work.
Monitor and respond
Live sessions and supported approvals, questions, and plans. Available actions depend on the agent and request.
More of your crew
Additional integrations offer live activity or detection and Jump. Approvals stay in the original app when a response connection is unavailable.
At home in your terminal, too
Jump back to the right window, tab, or tmux pane. Custom terminal rules are available in Settings. How Jump works.
Pricing
All your sessions, close at hand.
$9.99$14.99
USD · one payment · one Mac
The whole app. Yours to keep.
A license is required to use the app. Terms · Privacy
Questions
Yes. CrewTower follows Claude Code sessions in the Claude app and Codex tasks in the ChatGPT app, alongside supported terminal and editor sessions. See progress, respond to supported requests, and jump back to the task.
No. CrewTower uses the notch when your display has one and a small pill at the top of other screens. It runs on macOS 15 or later.
Use the to explore sample sessions, approvals, plans, and companions. The Mac app requires a license and has no free trial.
CrewTower offers approvals, questions, and plan review when the agent provides a supported response connection. Other integrations show activity or detection and let you Jump back. If a request cannot be answered in the notch, continue in its original app.
No. Supported answers go directly to the waiting session through its local connection. CrewTower does not type into your apps. Jump brings you back when you need to continue there.
CrewTower does not upload your prompts, code, or transcripts. It makes network requests for licensing, updates, and enabled provider usage checks. There is no CrewTower account or app analytics. The privacy policy explains those connections.
Activating CrewTower configures supported integrations in the agents you have installed. It adds the hooks or plugin needed to follow sessions and answer requests. Your own integrations are preserved.
Accessibility helps Jump find the right terminal tab and navigate supported desktop sessions. Approvals and answers use a separate connection and do not depend on that permission.
Claude Code, Codex, and Cursor keep their own prompts available. Gemini CLI and Qwen Code receive an explicit denial if CrewTower cannot respond, so a missing response is never treated as your approval.
Yes. Sessions keep their own titles and status, even when they share a folder. You can tell them apart in the notch and jump back to the one you need.
Your apps. Your workflow. A little less checking. Bring your crew together at the top of your Mac.
One payment. Updates included.