v3.0· Single Rust Binary· Native-Only MCP Relay

Codex Browser Use
and Computer Use
for any MCP client.

A local stdio MCP and CLI relay for the installed Codex node_repl (Browser Use) and cua_repl (Computer Use) runtimes — one stateless relay, no profile copies, no second extension.

Claude Code plugin
claude plugin install codex-browser --marketplace DeliciousBuding/codex-browser-bridge
MIT · Windows / Linux / macOS binaries · npm or standalone executable
//Two entries

Two native runtimes, one thin relay.

The plugin and client templates register Codex's installed node_repl and cua_repl runtimes directly. The bridge discovers each launch row, owns one worker, and forwards MCP frames unchanged.

--surface native-browser Primary · Browser

Installed Browser Use
via Codex node_repl.

Relays the installed [mcp_servers.node_repl] service over stdio so external MCP clients use the official Browser/Chrome plugin JavaScript API, backend selection, and permissions.

// bootstrap once per node_repl worker const { setupBrowserRuntime } = await import(pluginClientUrl); const agent = await setupBrowserRuntime(); const browser = await agent.browsers.get(browserId); nodeRepl.write(await browser.documentation());
  • Reads [mcp_servers.node_repl] from ~/.codex/config.toml (or --native-config) without modifying user config.
  • Preserves the runtime's own catalog, schemas, images, and bidirectional elicitation/create approval prompts.
  • Reports boolean browser_access_env diagnostics in discover/doctor without exposing host token values.
  • Runs turn_ended cleanup and closes the owned worker process tree on EOF, SIGINT, or SIGTERM.
--surface computer Primary · Desktop

Installed Computer Use
via Codex cua_repl.

Discovers and relays the installed Codex cua_repl service for desktop windows and unified browser targets, preserving host env policy, tool filters, and cleanup.

// stateful cua runtime over one worker const wins = await cua.listWindows(); const app = await cua.getApp({ windowId: wins[0].windowId }); const state = await app.getAXStateAndScreenshot(); await app.click(state.elements[0].index);
  • Discovers [mcp_servers.cua_repl] in Codex config or the generated unified-computer-use .mcp.json.
  • Full-duplex, cancel-safe JSON-RPC stdio relay with bidirectional elicitation/create application approval passthrough.
  • CLI call and batch modes support --image-dir artifact capture while preserving original base64 blocks; --omit-inline-images drops the base64 payload once files are saved.
  • Windows Job Object / Unix process-group teardown; timed-out or interrupted calls are never replayed.
Clients
Claude Code · Cursor
Antigravity · OpenClaw · shell
The bridge
codex-browser-bridge
one Rust binary · stdio
Two entries
--surface native-browser → node_repl
--surface computer → cua_repl
The Claude plugin and client examples register both native services. Omit --surface to use native-browser. The bridge does not implement CDP, DOM, locators, or browser sessions.
//Quick setup

Register the runtimes you use.

The Claude plugin registers native Browser Use and Computer Use separately. Manual configurations can keep both or just one entry; each server exposes only its installed runtime's catalog.

Zero-config for Claude Code, explicit everywhere else

The plugin installs the skill and MCP server together. Manual clients get the same binary over stdio — the plugin is a wrapper, not a different implementation.

terminalshell
# marketplace + plugin + skill in one step
claude plugin install codex-browser --marketplace DeliciousBuding/codex-browser-bridge

# standalone binary or npm, if you prefer
npm i -g @delicious233/codex-browser-bridge
mcp.jsonjson
{
  "mcpServers": {
    "codex-browser": {
      "command": "codex-browser-bridge",
      "args": ["--surface", "native-browser", "--mode", "mcp"]
    },
    "codex-computer": {
      "command": "codex-browser-bridge",
      "args": ["--surface", "computer", "--mode", "mcp"]
    }
  }
}
//Tool catalog

Whatever the installed runtime advertises.

Each native entry exposes the tool names its installed node_repl or cua_repl provides (commonly js, js_reset, js_add_node_module_dir, turn_ended). The list below documents those native hooks; the runtime's own documentation is the API reference.

//Trust model

Thin adapter. Hard boundaries.

This binary holds the keys to a logged-in browser and a desktop session. Every design choice assumes that.

The runtime is the surface

Tools, schemas, errors and approvals are the installed node_repl or cua_repl's own. The bridge adds no second vocabulary that could drift from it.

Bounded relay

Fixed frame and backlog limits: 64 MiB per frame, 8 MiB and 256 frames of outbound backlog per side, 1 MiB per batch line. Writes time out after 10 seconds; full buffers pause reads instead of growing without bound.

No replay

A timeout is an unknown outcome, not a retry token. The relay never resends a tool call; inspect the runtime state before deciding what happened.

Deterministic cleanup

EOF, SIGINT and SIGTERM cancel in-flight work, send turn_ended, close stdin, then tear down the owned process tree — Job Object on Windows.

Host-owned handshake

The client's initialize, version negotiation, pagination cursors and request deadlines pass through to the runtime. The bridge does not normalize or re-negotiate the MCP handshake.

Local-only by design

No network port, no telemetry, no hidden fallback runtime. CDP and desktop access come from the installed runtime's own API, not from a second bridge-side control plane.

Use your installed Codex runtimes from any MCP client.

Install the Claude Code plugin to register codex-browser (node_repl) and codex-computer (cua_repl), or configure either service manually in your MCP client.

claude plugin install codex-browser --marketplace DeliciousBuding/codex-browser-bridge