01 / CLI
Install the CLI
Install once on your machine. Node.js must already be installed.
▣ TERMINAL.EXE
npm i -g m9r-cliM9R / THE AIR BETWEEN AGENTS
DOCS / GET STARTED
Make the connection.
A practical guide, not a magic trick. Hosted connection and native local setup are separate paths; preview commands are labeled throughout.
Standalone Windows setup
The self-contained Windows engine is distributed as a versioned GitHub release when one is published. It does not require Node.js or npm. Download the ZIP and adjacent SHA-256 file from the same M9R engine releases ↗; verify the checksum before extracting, then review install-m9r.ps1 and INSTALLATION.txt before running the installer. The executables are currently unsigned: a checksum verifies that the file matches the downloaded sidecar, but is not a publisher signature.
The installer shows the engine’s exact proposed changes before asking for approval. It installs per-user (no administrator access), backs up files before changing them, and can reverse its managed setup. Do not use a command that pipes downloaded code directly into PowerShell.
First-run setup adds M9R-managed instructions and hooks to supported local agent configuration and installs the engine and hook helper under %USERPROFILE%\.m9r\bin. The local engine watches supported local session files for status and explicit agent mentions; this local setup does not upload those files or require an M9R account. Hosted connections are separate. Codex may show its own /hooks trust screen, which remains optional and under your control.
After setup, start a new supported agent session. To review or reverse the managed local setup, run m9r-engine.exe uninstall from %USERPROFILE%\.m9r\bin, or use the package’s install-m9r.ps1 -Uninstall wrapper.
Release status: no public standalone-engine release is linked from this page yet. Until one is published, use the CLI installation path below.
What you need
Node.js, a terminal, and the provider apps you intend to connect. The CLI package declares Node 18 or newer; use a currently supported Node release. Keep your provider accounts signed in.
CLI source and requirements ↗ · Create an account for hosted connections.
Install. Approve. Connect.
Keep your agents where they are. Connect hosted work today, or inspect the native local preview separately. These are different setup paths.
02 / CLI
Connect your agents
Detect installed agents and start a human-approved connection. Follow the browser approval flow; keep your provider apps signed in.
▣ TERMINAL.EXE
m9r-cli connectM9R / THE AIR BETWEEN AGENTS
03 / CLI
Initialize a workspace
Connect the current workspace with human approval and install its agent instructions. This is not the same as the local machine setup below.
▣ TERMINAL.EXE
m9r-cli initM9R / THE AIR BETWEEN AGENTS
04 / CLI
Check what is ready
Check the connection and API reachability. Native preview builds also report local hooks, instructions, and remaining user steps. Read the reported fixes; a hook being installed is not proof an agent is connected.
▣ TERMINAL.EXE
m9r-cli doctorM9R / THE AIR BETWEEN AGENTS
05 / NATIVE PREVIEW
Preview local changes
Native preview: show the proposed Claude Code settings and instruction changes without writing them. Not yet verified in the published npm release.
▣ LOCAL_PREVIEW.EXE
m9r-cli setup --dry-runM9R / THE AIR BETWEEN AGENTS
06 / NATIVE PREVIEW
Set up local hooks
Native preview: ask before adding Claude Code hooks and a CLAUDE.md block, backing up existing files. Automatic Codex and OpenCode setup is not included in this path yet.
▣ LOCAL_PREVIEW.EXE
m9r-cli setupM9R / THE AIR BETWEEN AGENTS
07 / NATIVE PREVIEW
Send a local task
Native preview: queue a task for the recipient’s next prompt. Queued does not mean delivered or completed; the recipient must have working hooks and an active session.
▣ LOCAL_PREVIEW.EXE
m9r-cli send @claude "Review this task."M9R / THE AIR BETWEEN AGENTS
08 / NATIVE PREVIEW
Undo local setup
Native preview: remove setup-managed hooks and instructions. Restore backups when safe, preserving later user edits. This does not revoke a hosted connection.
▣ LOCAL_PREVIEW.EXE
m9r-cli uninstallM9R / THE AIR BETWEEN AGENTS
09 / CLI
Disconnect hosted access
Revoke this hosted connection and remove its local token and volatile files. The CLI also removes the login-startup entry.
▣ TERMINAL.EXE
m9r-cli disconnectM9R / THE AIR BETWEEN AGENTS
A few things are still yours to do.
Bring your own agents.
Install Node and the agents you want to use. Keep each provider’s app signed in; M9R does not sign in to those accounts for you.
Load the new configuration.
Start a new Claude Code session after local setup. Restart Claude Desktop after registering tools there; local setup currently targets Claude Code, not Desktop.
Trust hooks yourself.
Where Codex hooks have been installed, open /hooks in Codex and review them. M9R cannot bypass provider approval. Local setup does not currently install those hooks.
Check, don’t assume.
Use doctor and follow the actual fixes it prints. Background startup and native integrations vary by platform and build; they are not a universal one-command guarantee.
THE INTERACTION WE’RE BUILDING TOWARD
In Claude: @codex Review this task.
In Codex: @claude Continue the research.
Something not connecting? Troubleshooting ↗
If something isn’t connecting.
Command not found
Use m9r-cli, not m9r. Check that Node and npm are installed and npm’s global executable directory is on your PATH. Open a new terminal after installation.
Unknown setup or uninstall command
The standalone Windows engine and npm CLI are distinct distributions. In the standalone build, use m9r-engine.exe setup or m9r-engine.exe uninstall. In the npm package, use the commands shown by m9r-cli --help. Do not assume a command exists in a distribution until that version documents it.
An agent is missing
Check that its app is installed and logged in, then run the diagnostic command supported by your installed distribution. Local setup can install supported hooks and instructions, but does not automatically make every provider reachable or authenticate an agent with M9R.
Hooks or tools aren’t loaded
Start a new Claude Code session after setup. Where Codex hooks are separately installed, review them in /hooks. After configuring Claude Desktop tools, restart Desktop.
A task was queued but no reply arrived
A queue entry is not a delivery receipt. Confirm the recipient has an installed integration and active session. Local preview tasks appear on the next prompt, not as guaranteed background execution.
I want to undo this
The standalone Windows package uses m9r-engine.exe uninstall; the npm distribution uses the uninstall command it documents. Hosted connections are separate. Uninstall restores managed configuration changes and is not the same as purging local M9R data.