Codex in your MacBook notch

A long run is only unattended until it is not

You give Codex something substantial and go do other work. That is the whole appeal. The catch is that a long run does not finish quietly on a schedule you can plan around: somewhere in the middle it hits a command it needs a human for, or it finishes twenty minutes before you thought it would, and either way it is sitting in a terminal tab behind everything else.

The cost is not the pause. It is the gap between the pause and the moment you happen to look. CrewTower closes that gap: the session's card comes forward in the notch with the exact command on it, wherever you are and whatever is full-screen.

What the run is doing, without opening it

Every running session gets a card: what it is doing right now, how long it has been going, and whether it is waiting on you. The ones waiting sort to the front, so a glance at the notch answers the question you would otherwise have answered by cycling through terminal windows.

Nothing about this is a dashboard you log into. It is on your Mac, in the notch, reading what your agents already write locally.

Answering without breaking your place

When an agent's hook blocks on the local Unix socket waiting for a decision, CrewTower answers over that same socket. The prompt resolves in place: your terminal never comes forward, and nothing is typed into it.

A destructive shell command is flagged on the card before you press anything, which matters more on a run you have not been watching than on one you have. And there are two ways to say yes: the button allows once, and the menu beside it allows every permission request for the rest of the session, a grant CrewTower keeps itself rather than a rule written into Codex's settings.

Land on the exact tab

When you do want the terminal, Jump takes you to that session's own place, not just the application: the exact tab in Terminal, iTerm2 (down to the split) and Ghostty; the pane in WezTerm, tmux and herdr, 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 a single line containing placeholders. 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. Answering from the notch does not need it.

Setup is one launch

Hooks are configured the first time CrewTower runs, and removed again when you delete the app. There is no file for you to edit and nothing left behind afterwards.

The next time that run stops for you, the card is in the notch.

It stays on your Mac

Sessions are read from what the agents already write locally, and decisions travel over a local socket. There are no accounts, nothing to log into, and no analytics in the app at all. Transcripts, prompts and diffs never leave the machine, and no session is visible from another one.

What it does not do

CrewTower shows how much of your subscription window is left, read from the Codex CLI's own rate limit reporting, plus how much context each session has left. What it does not do is keep a token or cost history: if you want a breakdown of what a run has spent, that is a different question and a different tool. It is not a terminal, not an IDE, and not a way to run agents - it watches and answers the ones you started yourself.

Questions

Does CrewTower work with Codex from OpenAI?

Yes. Codex is one of the agents CrewTower speaks to natively, in a terminal and in the ChatGPT app. Its sessions appear in the notch with what they are doing and how long they have been running, and CrewTower offers full decision support wherever Codex exposes a decision channel.

Can I leave a long Codex run unattended?

That is what CrewTower is for. You do not have to keep the terminal in view. When the run stops for a human, the card comes forward in the notch with the command on it, so the pause reaches you instead of sitting there unnoticed.

Does it handle several Codex sessions at once?

Yes. Each running session gets its own card, and the ones waiting on a human sort to the front.

Do I have to configure Codex hooks by hand?

No. CrewTower configures hooks on first launch and cleans them up when you remove the app. There is no config file to write yourself. Codex runs a hook only once you have reviewed it, and Settings > Integrations shows whether Codex has accepted CrewTower's.

Does answering from the notch type into my terminal?

No. The answer travels back down the socket the hook is already blocking on. There is deliberately no synthetic-keystroke path anywhere in the app.

How do I get Codex notifications on my Mac without CrewTower?

Codex has two settings of its own in ~/.codex/config.toml: [tui] notifications, which makes the terminal UI post a notification when a turn ends or an approval is waiting, and a root-level notify program that runs when a turn completes. The Codex notifications guide has both, tested.

Does CrewTower show Codex usage?

It shows how much of your subscription window is left: the session window and the weekly window, as a percentage used with a countdown to the reset, taken from the Codex CLI's own rate limit reporting. The meter is on by default and can be turned off in settings, and it also shows how much context each session has left. It keeps no token or cost history by day, session or model, and shows no cost for Codex sessions. For that, ccusage is the tool most people use.

Does it work with other agents at the same time?

Yes. Claude Code, Cursor, Gemini CLI, Qwen Code and opencode are all 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.