Codex and Cursor notifications on your iPhone
Updated
Quick answer
Codex can reach your iPhone with Monish in two ways: a line in AGENTS.md tells it to send results, progress and questions, and a PermissionRequest hook rings your phone when Codex waits for an approval. It is free and needs no account. The Codex approval itself is still answered in Codex.
What Codex and Cursor do on their own
- Codex
notifyruns a program of your choice, but only onagent-turn-complete: one call per finished turn, and nothing when Codex waits for your approval. - Codex
tui.notificationscan alert you onapproval-requested, in the terminal on your computer. - Codex hooks, on by default in current versions, include a
PermissionRequestevent that fires before Codex asks for an approval. - Cursor reads
AGENTS.mdat the root of the project and rules in.cursor/rules, as described in its docs.
None of these reaches your phone by itself. Monish is the part that does: one HTTPS endpoint the agent calls with curl. For Claude Code, Monish pairs with one command instead, curl -fsSL https://monish.cc/install.sh | sh -s with the code from the app; for Codex and Cursor, the agent reads a short skill and calls the endpoint itself.
Codex in three steps
-
Install Monish
Free on the App Store, for iOS 17.2 or later, with no account. The app creates a private key for this iPhone. On the pairing screen, tap Using Codex, Cursor or a script? to get the line to paste.
-
Paste the line in Codex
Set up my agent notifications with key an_•••••••••• — follow https://monish.cc/skill/an_••••••••••
Codex reads the skill, saves the key in
~/.config/monish/keyand sends a first notification, “Connected”. -
Add one rule to AGENTS.md
Codex can load skills from
~/.agents/skills, but one line in the project’sAGENTS.md(or~/.codex/AGENTS.mdfor every project) is the simplest way to tell it when to reach you:When a task longer than a minute finishes, fails, or needs my decision, call the Monish endpoint as described in https://monish.cc/skill with the key in ~/.config/monish/key. One item per task, same id for progress then done.
Optional: ring when Codex waits for an approval
A PermissionRequest hook fires before Codex asks you to approve a command. This one sends “Needs you” and prints nothing, so Codex then asks you as usual and you answer in Codex. Repeated approvals in the same project update one line instead of stacking.
Save as ~/.codex/hooks.json (or merge into an existing one)
{
"hooks": {
"PermissionRequest": [
{
"hooks": [
{ "type": "command", "command": "~/.config/monish/codex-hook.sh", "timeout": 10 }
]
}
]
}
}
Save as ~/.config/monish/codex-hook.sh, then chmod +x it
#!/bin/sh
# Monish: notify the phone when Codex waits for an approval. Prints nothing, so Codex still asks as usual.
key="${MONISH_KEY:-$(cat ~/.config/monish/key 2>/dev/null)}"; [ -z "$key" ] && exit 0
input=$(cat)
cwd=$(printf '%s' "$input" | jq -r '.cwd // ""' 2>/dev/null); project=$(basename "${cwd:-$PWD}")
tool=$(printf '%s' "$input" | jq -r '.tool_name // "a command"' 2>/dev/null)
jq -nc --arg k "$key" --arg p "$project" --arg t "$tool" \
'{key:$k,id:(("codex-"+($p|gsub("[^A-Za-z0-9_.:-]";"-")))[0:64]),type:"done",title:("Needs you · "+$p),body:("Codex is waiting for your approval: "+$t),agent:("Codex · "+$p),fields:{severity:"warning"}}' \
| curl -s -m 5 https://monish.cc/v1/send -H 'content-type: application/json' -d @- >/dev/null
exit 0
Codex runs a new or changed hook only once you trust it: open Codex, run /hooks and trust this one. Leave notify alone: a notification for every finished turn is noise, and the real result belongs to the done item Codex sends itself.
Cursor in three steps
-
Install Monish
The same app and the same key: one iPhone can hear from Claude Code, Codex and Cursor at once.
-
Paste the line in Cursor’s agent chat
Cursor’s agent reads the skill, saves the key and sends “Connected”.
-
Add the rule
Put the same line in
AGENTS.md, or in a project rule that always applies:Save as
.cursor/rules/monish.mdc--- description: Monish notifications alwaysApply: true --- When a task longer than a minute finishes, fails, or needs my decision, call the Monish endpoint as described in https://monish.cc/skill with the key in ~/.config/monish/key. One item per task, same id for progress then done.
The rule asks for one item per task, updated in place: progress first, then done or failed under the same id. A long task stays one card on your lock screen instead of a stack of notifications, and the agent decides on its own what is worth sending, which is why the rule mentions only tasks longer than a minute.
What lands on your iPhone
- Progress stays live on the lock screen and in the Dynamic Island, as a Live Activity updated in place.
- Done or failed arrives as one notification per task. A failure can still ring during your quiet hours.
- Questions come with Approve and Deny, or two labels of the agent’s choice. How questions work.
- Numbers, two to four figures, can stay live on the lock screen.
What Codex itself asks you, such as approving a command, is still answered in Codex: the hook above only tells your phone that Codex is waiting. To make Codex wait for your tap before something that matters, tell it in AGENTS.md to ask you through Monish first, as in the question below.
Questions
- Does Codex’s notify setting reach my iPhone?
- Not by itself.
notifyruns a local program after each finished turn. You could point it at Monish, but a notification per turn is noise; theAGENTS.mdrule lets Codex send one useful item per task instead. - Will Codex ask me before it deploys?
- If you tell it to. Add “Before you deploy, send or spend, ask me with Monish first” to
AGENTS.md. Codex sends a question, waits for your tap, and reads Deny or no answer as a no. - Does the Claude Code install command set up Codex?
- No. It adds Claude Code hooks. Codex and Cursor use the line to paste and the
AGENTS.mdrule, with the same app and the same iPhone. - Can one iPhone hear from several agents?
- Yes. Every item carries the agent’s name, such as Codex · lumen or Cursor · web, so you know who is talking.
More guides
- Claude Code notifications on your iPhone: setupPair in one command, then allow, deny or reply from the lock screen.
- Approve or deny from the lock screen, from any scriptFor Codex, Cursor, n8n and scripts: what a question carries, the JSON.
- n8n notifications on your iPhoneOne HTTP Request node: end of a workflow, errors, approval before an email.
- Claude Code notifications: six ways, comparedThe terminal bell, your own hooks, ntfy, Remote Control and notifier apps.
New to Monish? The home page shows what lands on your iPhone, and all guides are listed here.
Get Monish on your iPhone
Free, no account. In the app, tap “Using Codex, Cursor or a script?” to get the line to paste.