Blog · · Dimitris Kyriakakis
Answer Codex permission prompts on a Mac without finding the terminal
Codex can sit in a terminal tab for minutes, waiting for a yes. With several agents open on a Mac, the slow part is noticing the prompt and finding the right window to answer it in.
What Codex gives you on its own
Codex can raise a desktop notification when it needs you. In ~/.codex/config.toml:
[tui]
notifications = ["approval-requested"]
true turns on every notification type. By default they fire only while the terminal is unfocused; notification_condition = "always" changes that. That covers knowing a prompt is there. To answer it, you still focus the session and answer in the terminal.
The notify setting runs a program of your choice, but only when a turn completes. It doesn't fire on approval requests. See the Codex config reference.
Hooks that answer
Codex has hooks, configured in ~/.codex/hooks.json. A PermissionRequest hook receives the request and can return allow or deny. If it returns no decision, Codex shows its usual prompt. That is the path a tool needs to answer Codex from somewhere other than the terminal.
Codex runs a user-level hook only once it is trusted. Read any hook before you trust it; it decides what runs on your machine.
What you usually want
- A banner you notice when Codex is blocked.
- Allow and Deny without finding the tab.
- The same habit when Claude Code or Cursor asks in the same hour.
- A way to answer when you've stepped away from the desk.
One queue with AgentNod
AgentNod puts Claude Code, Codex and Cursor in one list on your Mac, oldest first. It answers Codex through the PermissionRequest hook. Setup writes the handler to ~/.codex/hooks.json and the matching trust entry to ~/.codex/config.toml, and saves a .before-nod copy of hooks.json first. For Codex:
- A notification names the session and what it wants, with Allow, Deny and Deny with a note on the banner. Codex reads the note as the reason for the denial, so "use pnpm" changes what it tries next.
- A destructive request offers Open and Deny on the banner, not Allow, so you read the command on the card first.
- The HUD docks to the notch or a display edge and opens when something needs you.
- From your phone: the Mac serves the queue as a page over your network or Tailscale, with no account. Push comes through ntfy, or, with AgentNod Pro, through the AgentNod iPhone app.
- Night watch keeps the Mac awake while agents work or wait on you.
You can still answer in the terminal. The arrow on a card hands the prompt back, and ⌘J jumps to the window it came from.
Claude's Remote Control doesn't cover Codex
Anthropic's Remote Control connects claude.ai/code or the Claude app to a Claude Code session on a paid Claude plan. It doesn't reach Codex. If your day mixes Codex with Claude Code or Cursor, a Claude-only remote leaves the other agents waiting in their tabs.
For the Claude options side by side, see Approve Claude Code permission prompts from your phone. For Mac notifications across agents, see Get a notification on your Mac when Claude Code needs you.