Skip to content

Make the
connection.

Use the supported two-command path first. The source-checkout broker and standalone engine are optional.

Quick start

Quick start

Install Node.js 18 or newer, keep the provider apps you want signed in, then run these commands from any terminal:

npx m9r-cli connect npx m9r-cli web setup npx m9r-cli doctor

connect finds Claude Code, Codex, and OpenCode and opens one browser approval. web setup installs the managed browser extension and local broker. doctor confirms the connection.

The only manual browser step is loading the copied %LOCALAPPDATA%\M9R\extension folder with Developer mode enabled. Use that same folder after updates; do not load a second repository copy.

Any terminal
Requirements

What you need

Node.js 18 or newer, a terminal, Chrome or Edge for browser work, and the provider apps you intend to connect.

Create an accountCLI source and requirements
Node.js 18+
Setup

Connect. Add the browser. Verify.

Two commands put your existing agents and the browser workspace on the same local bridge. Keep each provider signed in; M9R does not replace or re-authenticate them.

The public setup uses npx m9r-cli. The source-checkout broker and native preview commands are troubleshooting or development tools, not extra installation steps.

Two commands, one approval
Terminal

Step 1 of 4

Connect your agents

Find the Claude Code, Codex, and OpenCode CLIs already on this machine and open one human approval.

npx m9r-cli connect
CLI
Terminal

Step 2 of 4

Add browser work

Install the managed browser extension, start the local broker, and load the one extension folder in Chrome or Edge.

npx m9r-cli web setup
CLI
Terminal

Step 3 of 4

Check what is ready

Confirm the saved connection and API reachability after setup.

npx m9r-cli doctor
CLI
Terminal

Step 4 of 4

Disconnect hosted access

Revoke the connection and remove its local token and temporary state.

npx m9r-cli disconnect
CLI
Your part

A few things are still yours to do.

  • Keep your providers ready.

    Install Node.js 18 or newer and the agent CLIs you want to use. Keep each provider app signed in; M9R never handles those logins.

  • Approve once.

    The connect command opens one browser approval for the providers it detects. Approve it, then let the command finish.

  • Load one extension folder.

    The web setup command opens the browser extension page. Turn on Developer mode and load the copied managed folder once.

  • Verify the connection.

    Run doctor if anything looks offline. Do not start the development broker or load a second extension copy.

4 manual steps
Mentions

The interaction we're building toward

Agents asking agents.

In Claude: @codex Review this task.

In Codex: @claude Continue the research.

End-to-end behavior depends on each recipient's installed integration; these examples are not proof of universal support.

Something not connecting? Troubleshooting
Illustrative, not shell commands
Engine

Optional standalone engine

The self-contained Windows engine is a separate distribution and is not required for the supported browser setup. Use it only when a versioned release is published from the M9R engine releases. Verify the adjacent SHA-256 file before running its installer. Do not pipe downloaded code directly into PowerShell.

Not required
Troubleshooting

If something isn’t connecting.

Command not found

Use the commands exactly as shown: npx m9r-cli .... Check that Node.js 18 or newer and npm are installed, then open a new terminal.

The browser extension is missing

Run npx m9r-cli web setup, load the copied managed folder in chrome://extensions or edge://extensions, and reload that same folder after an update.

An agent is missing

Install the provider CLI, sign in to its own app, and run npx m9r-cli connect again. M9R does not sign in to providers for you.

The connection looks offline

Run npx m9r-cli doctor. If it reports that no connection exists, run npx m9r-cli connect again and approve the browser request.

I want to undo this

Run npx m9r-cli web uninstall to remove the managed browser setup, or npx m9r-cli disconnect to revoke the hosted connection and remove its local token.

5 common fixes