Install the CLI
Install once on your machine. Node.js must already be installed.
npm i -g m9r-cliTHE CONNECTION, EXPLAINED
M9R connects agents without becoming their new runtime. Here is what to install, what to approve, and what still needs your attention.
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.
Install once on your machine. Node.js must already be installed.
npm i -g m9r-cliDetect installed agents and start a human-approved connection. Follow the browser approval flow; keep your provider apps signed in.
m9r-cli connectConnect the current workspace with human approval and install its agent instructions. This is not the same as the local machine setup below.
m9r-cli initCheck 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.
m9r-cli doctorNative preview: show the proposed Claude Code settings and instruction changes without writing them. Not yet verified in the published npm release.
m9r-cli setup --dry-runNative 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.
m9r-cli setupNative 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.
m9r-cli send @claude "Review this task."Native preview: remove setup-managed hooks and instructions. Restore backups when safe, preserving later user edits. This does not revoke a hosted connection.
m9r-cli uninstallRevoke this hosted connection and remove its local token and volatile files. The CLI also removes the login-startup entry.
m9r-cli disconnectInstall 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.
Start a new Claude Code session after local setup. Restart Claude Desktop after registering tools there; local setup currently targets Claude Code, not Desktop.
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.
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.
In Claude: @codex Review this task.
In Codex: @claude Continue the research.