Skip to main content
Most of what looks like a bug here is Nomo being honest about not knowing something. This page is what each of those states actually means, grouped by where you’d go to fix it. If more than one thing looks wrong at once, skip ahead and start with status — it usually names the problem in one screen.

​
Fix it on your phone

Nothing to do at your Mac for any of these.
Almost always the intended behaviour: sessions are opt-in. Open the computer, find the session, flip its switch — or turn on Auto add new sessions in Settings.If the switch is on and still nothing shows, check Live Activities is enabled for Nomo in iOS Settings. Then check that another session isn’t holding the island: your phone shows one at a time, and a session that has been waiting on you outranks one that’s working.
That session is asking permission. A prompt reaches your island whichever way its switch is set — otherwise a prompt that arrived while your phone was in your pocket would be one you couldn’t answer, which is the whole point of the feature. So the switch shows on while the prompt waits, because that’s what’s actually happening.Why you can’t turn it off: turning it off wouldn’t do anything. The prompt would stay on the island regardless — that’s the only way it can reach you — so the switch would flick back on under your thumb a second later. Rather than give you a control that ignores you, Nomo holds it still until it can obey you again.Nothing you chose was overwritten. Answer the prompt and the switch goes straight back to off, where you left it — or within the hour, if nobody answers. Then it’s yours to set again.None of this happens with Remote approvals off, which is the default: your switch is never overridden. See Answering from your phone.
The island shows the last thing your Mac sent. After ten minutes of silence it drains of colour and says Disconnected? rather than continuing to imply the session is live.Your Mac asleep, off the network, or the terminal closed all land here. Open the Nomo app to force a refresh — a stale state corrects itself immediately. If it doesn’t, the Mac genuinely isn’t reporting: run the status command below.
Check the colour, not the icon. Yellow and violet both draw a raised hand. Yellow (Need help) means the agent stopped for something only the terminal can take. Violet (Needs permission) is the answerable one.If everything is yellow and never violet, Answer on iPhone is probably off — it’s off by default. See Answering from your phone.

​
Fix it on your computer

Your phone is fine. These are all settled from a session on the Mac.
Someone ran the pause command on that computer. Resume it from a session on that machine:
One switch per computer, shared by both agents — more.
Codex hooks ship inert until trusted, and a plugin update that adds a hook re-opens that review. Run /hooks in Codex and trust the Nomo entries. Until you do, approvals fall back to the terminal and nothing reports an error.More in Using Codex.
Always allow, Deny with note… and Answer… all need plugin 2.0.0 — answering from the phone is what 2.0 added. Nomo hides options the Mac can’t honour rather than offering a button that would do nothing.A Plugin update available banner at the top of the drawer means exactly that. Update from the same command you installed with.
Clear the dead ones without unpairing:
Live sessions, your pairing and your keys are left alone — what it prints.

​
Pairing and decryption

Your phone is receiving updates it can’t read, or a computer it no longer has a key for. All three end at the same fix: pair that computer again.
Your phone received the update but hasn’t unlocked it yet. Nomo retries every few seconds, and this usually clears itself within one poll.If it persists, your phone no longer holds the right key for that computer — the Mac was re-paired, or the pairing was replaced. Pair it again.
The same thing, after ten minutes of failing. Rather than leaving a row that looks alive but isn’t, Nomo marks it dead and stops guessing at its contents. It won’t drive the island and it won’t be counted as active. Re-pairing the computer restores it.
That pairing was revoked — you re-paired the Mac, or ran /nomo-cc:unpair on it. Nomo waits for a sustained run of failures before believing it, so this is never a flaky-minute-of-Wi-Fi diagnosis.Tap Remove, or leave it — it clears itself about a minute later. Pair the computer again when you want it back.

​
Start with status

If more than one thing looks wrong, run /nomo-cc:status on the Mac before anything else. One screen tells you whether the machine is paired, whether its watchdog is alive, and whether events are actually reaching your phone — which is usually enough to say what’s broken. Last event sent: never with a session genuinely running means the hooks aren’t firing. Restart Claude Code so they load; for Codex, run /hooks. Every command, and what its output means, is on Commands.

​
Still wrong? Send it over

Turn on Session diagnostics in Settings, then expand the session that’s misbehaving. A line of Nomo’s own internal state appears underneath it, something like:
Don’t try to decode it — that’s our job. Screenshot the row and send it, along with what you expected and what you got instead:

Open an issue

Best for anything reproducible. Public, so leave out anything private.

Email

Also in the app, under Settings → Contact.
The output of /nomo-cc:status from the affected computer helps too.

​
Nothing’s broken — you just want something

“Why can’t I do X from my phone?” is often a fair question rather than a bug. Some of it is a real limit of what an agent hands to a plugin, and that’s written down: Using Codex covers the Codex side, and Answering from your phone covers what a Live Activity can and can’t host. The rest is just not built yet.

Check the roadmap

What’s planned and what’s in progress. Your idea may already be on it.

Ask for it

Open an issue, or email me. Tell me what you were trying to do — that’s more useful than the feature you’d designed.

​
Starting over

/nomo-cc:unpair on the affected computer removes the pairing and erases its key. Then pair it again. Forgetting a computer from the phone is not the same thing: it stops that computer appearing in your app, but the Mac keeps its local state until you run that command there.