SetupConnect. 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.
TerminalStep 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 connectTerminalStep 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 setupTerminalStep 3 of 4
Check what is ready
Confirm the saved connection and API reachability after setup.
npx m9r-cli doctorTerminalStep 4 of 4
Disconnect hosted access
Revoke the connection and remove its local token and temporary state.
npx m9r-cli disconnectYour partA 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.
MentionsThe 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.