Codex is not stuck.
It is waiting on you.
Pushary sends a push notification when Codex finishes or needs your permission, and lets you approve from your phone in one tap.
Codex tells your notify script when a turn ends, never when a command is blocked on your approval. Pushary sends that moment to your phone and holds the call until you answer.
One command
npx @pushary/agent-hooks@latest setupPick Codex when prompted. Enforced approvals need Codex 0.122 or newer.
Why do I get no Codex notification when it is waiting for my approval?
The program you set in Codex's notify config receives exactly one event, agent-turn-complete, so it fires when a turn ends and never when a command is blocked on your approval. Approval alerts stay inside the terminal UI. Pushary gates through Codex's PreToolUse and PermissionRequest hooks instead, so on Codex 0.122 or newer the pending command goes to your phone and waits for your answer. The hooks cover shell commands and apply_patch edits, which is most of what an agent does, but not every tool path.
Updated
Building an AI product for other people? Let your users approve what your agent does, from their phone. See the Partner plan or the human-in-the-loop API.
Featured on Hacker NewsWhy your notify script stays quiet
The legacy notify handler receives one event, agent-turn-complete. An approval request is not that event, so the moment you need to know about never leaves the machine.
Stop watching Codex spin. Start getting notified.
One command. Your phone buzzes when Codex is done.
Start your trialCodex notification questions
How do I get notifications when Codex finishes?
Run npx @pushary/agent-hooks setup and pick Codex. It connects Codex over MCP and installs native hooks, so your phone is notified when a task completes.
Can Codex ask me to approve a command from my phone?
Yes. On Codex 0.122 or newer, Pushary installs hooks that route risky shell and file-edit approvals to your phone. You tap yes or no and Codex continues.
Does this need a specific Codex version?
Enforced approvals need Codex 0.122 or newer. On older versions you still get notifications through the legacy notify handler, without the policy engine.
Is the approval gate airtight?
Treat it as a strong guardrail, not a security boundary. Codex hooks cover shell commands and apply_patch edits, which is most of what an agent does, but not every tool path.
Does Pushary answer Codex's questions, or gate its commands?
Commands, and the line between them is worth being exact about. Pushary gates the approval path, pre_tool_use and permission_request, where a command is held until your answer comes back and no timer is running against you. Codex's separate request_user_input overlay is the one that resolves itself after 60 seconds (openai/codex#28969, open, 199 reactions), and no hook can answer it today: the updatedInput field that would carry a reply is marked reserved in Codex's own hook schema, and a hook that sends it fails closed. If that opens up, this is the first place it lands.
Codex keeps asking about commands I already approved. Why?
Approvals that look like they should persist often do not, and repeated prompts despite auto-approve settings is a long-running open issue (openai/codex#10187). Pushary's policy engine matches on the command itself, so a rule you write once auto-clears the safe calls and only what falls outside it reaches your phone.
How much does Pushary cost?
Paid agent plans start with a 3-day trial at $9.99 per month, including 5,000 notifications per month.
Guides
Stay in control
Compare
Also works with