Installation

Install once per computer. You need bun or node 18+ — the plugin has no npm dependencies and runs on Node built-ins.

Install by hand

Claude Code
Codex
OpenCode

Terminal
Desktop app

From inside a Claude Code session:

/plugin marketplace add KarrixLee/nomo
/plugin install nomo-cc@nomo

Settings → Plugins → Add → Add marketplace. Put the repository in URL:

KarrixLee/nomo

Then Sync, and install Nomo — Claude Code from the list.

The Claude desktop app's Add marketplace dialog with KarrixLee/nomo entered as the URL — A GitHub owner/repo is enough — Nomo's repository is the marketplace.

Restart Claude Code afterward so the plugin’s hooks load.Confirm it’s there:

/nomo-cc:status

All Nomo commands in Claude Code are namespaced nomo-cc: — typing /nomo-cc: will list them, and so does Commands.

Codex 0.142 or later ships its own plugin system, so Nomo installs as a standalone Codex plugin. Claude Code is not required.

Install the plugin

Terminal
Desktop app

From inside a Codex session:

codex plugin marketplace add KarrixLee/nomo
codex plugin add nomo@nomo

The desktop app’s built-in terminal works too, if you’d rather type than click.

Plugins → Add → Add plugin marketplace. Put the repository in Source:

KarrixLee/nomo

Leave Git ref and Sparse paths alone — the grey text in them is placeholder, not a value you need to match. Then Add marketplace, and install nomo from the list.

The Codex desktop app's Add plugin marketplace dialog with KarrixLee/nomo entered as the source — Nomo's repository is the marketplace — there's no listing to browse or submit to.

“Marketplace” here isn’t a store you browse. It’s a registry pointed at a GitHub repository — Nomo’s own. That’s why you add the repo first, then install the plugin from it.

Trust the hooks — required

Terminal
Desktop app

/hooks

Trust the seven Nomo entries.

Don’t skip this. Nomo’s hooks ship with the plugin but stay inert until trusted. Until you do it, the plugin is installed and doing nothing — no sessions reach your phone, and nothing reports an error.

This is Codex’s own safety gate, and Nomo can’t pre-approve it. The hook command lines are byte-stable across releases, so trusting once holds through updates — only a changed hook line re-opens the review.

Confirm

$nomo-status

This reports pairing, watchdog, hook-trust, and last-delivery health — so it’s also how you check the trust step actually took.

Codex skills use a $ prefix rather than a slash. All five are listed in Commands.

OpenCode has no marketplace and no plugin command — it picks up whatever it finds in its own config folders. So Nomo installs from a clone, and one script puts the files where OpenCode already looks.

Clone it and run the installer

git clone https://github.com/KarrixLee/nomo.git ~/.nomo
~/.nomo/plugin/scripts/opencode-install.sh

Clone it wherever you like — the script works out its own location, so there’s no path to look up and nothing to hand-edit. It prints exactly what it wrote:

~/.config/opencode/plugins/nomo.js — a one-line stub pointing back at the clone.
~/.config/opencode/commands/nomo-*.md — the six commands.

Already installed Nomo for Claude Code or Codex? Point the script at that copy instead of cloning a second one — claude plugin list or codex plugin list prints where it lives.

--project installs into ./.opencode for one repository instead of globally. Re-running is safe, and it’s also how you move the clone: run it again from the new location.

Restart OpenCode — required

OpenCode imports plugins once, when its server starts, and there’s no hot reload. Until you quit and reopen it, the plugin is installed and doing nothing. The desktop app runs that same server, so it needs the same restart.

Confirm

/nomo-status

That one install covers the OpenCode desktop app as well: it runs OpenCode’s own server, which reads the same plugin folder.

Updating later is one command from inside OpenCode: /nomo-update checks first, then pulls and re-runs this installer — what it does, and when it refuses.

OpenCode command names are flat and global, so Nomo’s carry no prefix at all: /nomo-pair, not /nomo-cc:pair or $nomo-pair. All six are in Commands.

What lands differently on your phone is in Using OpenCode.

One command

The installer detects which of Claude Code, Codex and OpenCode are on this machine and sets Nomo up in the ones you pick:

bunx nomo-ai

npx nomo-ai

Nothing is ticked at the start: arrow keys (or k / j) move, space ticks an agent, enter installs everything ticked. Then it runs each agent’s own install — the same three flows above. Nothing is installed globally and no package is left behind. For scripting and CI:

Flag
`--claude` `--codex` `--opencode`	install exactly these — naming any one of them skips the picker
`--all`	all three, detected or not
`-y`, `--yes`	no picker; install everything detected
`-n`, `--dry-run`	print the commands, run nothing

It never pairs your phone. Finish exactly as the steps above describe: restart the agent, trust the hooks if it’s Codex, and pair — /nomo-pair, or /nomo-cc:pair in Claude Code and $nomo-pair in Codex.

Updating

The same command updates: an agent that already has Nomo shows up as an update rather than an install. Only OpenCode’s runs — the other two are printed for you.

Claude Code
Codex
OpenCode

claude plugin update nomo-cc@nomo

Auto-update defaults off for third-party marketplaces, so nothing moves an install on its own. To turn it on: /plugin → Marketplaces → Nomo’s → Enable auto-update.

Usually nothing to run. Codex reads the plugin live from its path, so pulling that checkout is the whole update — and there is no codex plugin update verb.If you added the marketplace from git, Codex holds a snapshot instead, and refreshing it is the update:

codex plugin marketplace upgrade <marketplace-name>

The name is whatever you added it as, not necessarily nomo.

The installer does it. So does /nomo-update from inside OpenCode.Either way, restart OpenCode afterwards — plugins are imported once at server start.

What the plugin does

It watches the session and reports state changes to your phone: what the agent is working on, when it stops, and when it needs permission for something. It sends nothing until you pair a phone, and everything it does send is encrypted on this machine first. The plugin is open source — you can read exactly what it collects and sends before you install it:

KarrixLee/nomo

The full plugin source, MIT licensed. Marketplace installs are a plain clone of this repository.

Pair your computer

Scan a QR code, or type a one-time code if you can’t open a browser.

Setup

On your phone

On your computer

Help

Installation

Install by hand

One command

Updating

What the plugin does

KarrixLee/nomo

Next

Pair your computer

​Install by hand

​One command

​Updating

​What the plugin does

KarrixLee/nomo

​Next

Pair your computer

Install by hand

One command

Updating

What the plugin does

Next