OpenBridge

中文说明

OpenBridge is a local browser bridge for AI agents. It lets MCP-capable clients and Codex-style skills control the user's real Chrome browser through a local daemon and a Chrome extension.

What It Does

OpenBridge provides a Kimi WebBridge-like architecture:

AI client / MCP client / Codex skill
        |
        | stdio MCP or local HTTP API
        v
OpenBridge daemon
        |
        | ws://127.0.0.1:10087/bridge
        v
OpenBridge Chrome extension
        |
        v
User's real Chrome tabs

The daemon is long-running, while openbridge mcp is a lightweight stdio shim that attaches to the daemon. This allows one browser connection to be reused by multiple local AI sessions.

Features

• Real Chrome tab control through a browser extension
• Automatic extension authorization after first connection
• Local-only daemon and API
• MCP stdio support
• Codex-style skill support through the local HTTP API
• Tab creation, navigation, selection, listing, and closing
• Session-based tab groups with color labels
• Accessibility snapshots with stable refs
• Click, coordinate click, fill, type, key input, and shortcuts
• Screenshot, PDF export, file upload
• Network event observation
• Pause control and optional JavaScript execution permission

Install

Security note: The quick install script below is convenient, but you should review it before running. You can also follow the manual steps to clone and inspect the code.

Quick network install:

curl -fsSL https://raw.githubusercontent.com/60ke/openBridge/master/install.sh | bash

NPM package:

npm install -g @openbridge-org/daemon
openbridge start

Install into a custom directory:

curl -fsSL https://raw.githubusercontent.com/60ke/openBridge/master/install.sh | \
  OPENBRIDGE_INSTALL_DIR="$HOME/.openbridge/repo" bash

Manual installation (review code before running):

git clone https://github.com/60ke/openBridge.git
cd openBridge
pnpm install
pnpm build
# Start the daemon
node packages/daemon/dist/cli/index.js serve

The installer will:

• install dependencies and build the daemon, shared package, and extension
• start the OpenBridge daemon in the background
• install the openbridge-webbridge skill for Codex-style clients
• print the Chrome extension loading path
• keep MCP available as an optional standard interface

Then load the unpacked Chrome extension from:

packages/extension/.output/chrome-mv3

Open chrome://extensions, enable Developer Mode, choose Load unpacked, and select the directory above.

After the daemon and extension are both running, the extension authorizes automatically. The popup should show Authorized. Codex can then use the installed skill to call http://127.0.0.1:10088/command directly, without requiring OpenBridge to appear in an MCP server list.

Installer options:

./install.sh --no-skill
./install.sh --no-start

The network installer accepts the same options:

curl -fsSL https://raw.githubusercontent.com/60ke/openBridge/master/install.sh | bash -s -- --no-start

Useful Commands

node packages/daemon/dist/cli/index.js start
node packages/daemon/dist/cli/index.js stop
node packages/daemon/dist/cli/index.js restart
node packages/daemon/dist/cli/index.js logs --follow
node packages/daemon/dist/cli/index.js serve
node packages/daemon/dist/cli/index.js mcp
node packages/daemon/dist/cli/index.js status
node packages/daemon/dist/cli/index.js doctor
node packages/daemon/dist/cli/index.js reset-pairing

Local API

The daemon exposes a local HTTP API on 127.0.0.1:10088 by default. If that port is occupied, OpenBridge automatically uses the next available port and writes the active runtime state to .openbridge-data/runtime.json.

Health check:

API_PORT="$(node -e "const fs=require('fs'); let p=10088; try { p=JSON.parse(fs.readFileSync('.openbridge-data/runtime.json','utf8')).apiPort || p } catch {} console.log(p)")"
curl -s "http://127.0.0.1:${API_PORT}/health"

Run a browser command:

API_PORT="$(node -e "const fs=require('fs'); let p=10088; try { p=JSON.parse(fs.readFileSync('.openbridge-data/runtime.json','utf8')).apiPort || p } catch {} console.log(p)")"
curl -s -X POST "http://127.0.0.1:${API_PORT}/command" \
  -H 'Content-Type: application/json' \
  -d '{"toolName":"browser_list_tabs","args":{}}'

MCP Config

The default smooth path is skill + daemon local API. MCP is still supported as a standard integration surface.

Example config is in openbridge-mcp-config.example.json.

{
  "mcpServers": {
    "openbridge": {
      "command": "node",
      "args": [
        "/absolute/path/to/openBridge/packages/daemon/dist/cli/index.js",
        "mcp"
      ]
    }
  }
}

Client Usage

OpenBridge can be used in two ways:

• skill + local API: the smooth default path for Codex-style clients
• MCP stdio: the standard path for clients that expect an MCP server entry

Codex

Codex is the primary default flow. After install.sh, OpenBridge installs the openbridge-webbridge skill into the local Codex skills directory. Once the daemon is running and the extension is connected, Codex can use the skill to call http://127.0.0.1:10088/command directly. The same path also fits Codex-style agent workflows that prefer local skills over MCP registration.

Claude Code

Claude Code can use OpenBridge in either mode:

• preferred: install the OpenBridge skill and let Claude Code call the local API
• optional: add the MCP config shown above if you want OpenBridge to appear as a standard MCP server

OpenCode

If OpenCode supports local MCP server configuration, use the openbridge mcp entry from the MCP example. If your OpenCode workflow supports Codex-style local skills or shell-driven helpers, you can also call the local API directly.

Kimi

Kimi itself already ships its own WebBridge stack. OpenBridge is not meant to replace Kimi's built-in browser bridge inside the Kimi product. The intended comparison is architectural: OpenBridge follows a similar daemon + extension + local API model, but as an open project.

CloudCode / Other MCP Clients

For any client that only knows how to consume MCP servers, use the MCP config and point it at:

node /absolute/path/to/openBridge/packages/daemon/dist/cli/index.js mcp --api-port 10088

For any client that can run local shell commands or use local skills, the local API path is usually the smoother option.

Browser Tools

OpenBridge currently supports:

browser_list_tabs
browser_new_tab
browser_select_tab
browser_navigate
browser_snapshot
browser_click
browser_mouse_click
browser_fill
browser_type
browser_key_type
browser_send_keys
browser_screenshot
browser_evaluate
browser_close_tab
browser_close_session
browser_find_tab
browser_upload
browser_save_as_pdf
browser_network

Security Model

• The daemon binds to loopback only.
• The extension connects only to the local daemon.
• Browser control can be paused from the extension popup.
• browser_evaluate is disabled by default and must be explicitly enabled.
• Pairing tokens are local machine state and should not be committed.
• .openbridge-data/ is ignored by Git.

Design Acknowledgments

OpenBridge's three-layer architecture (daemon + extension + local API) follows the proven model pioneered by Kimi WebBridge (Moonshot AI). Key design influences include session management patterns inspired by CodeX (OpenAI) and the tool-registry approach from Kimi WebBridge. OpenBridge builds on these concepts as an independent open-source project.

Development

pnpm install
pnpm typecheck
pnpm build

Reload the unpacked extension after rebuilding:

packages/extension/.output/chrome-mv3