dsh-chrome-bridge

= 116" />

= 18" />

English ·

简体中文 ·

Development notes

---

Give your DSH agent hands inside the Chrome you are already using — your logins, your tabs, your session. Install once, no Connect button, ever.

> What it is: a DeepSeek Harness (DSH) plugin that lets the model operate the Chrome you already use: open pages, click, type, fill in forms, read pages, take screenshots and work across tabs, with your existing logins.

>

> Use it for: "fill in this web form", "check this admin page for me", "screenshot this site", or anything else the model has to do inside a browser.

>

> Install: on the DSH Plugins page, click Add plugin and enter dsh-chrome-bridge (an npm package), restart DSH, then add the DSH Bridge extension from the [Chrome Web Store](https://chromewebstore.google.com/detail/bippcbbbipppmhjkjomgdnjbooecbimo). Needs macOS, Windows or Linux, Chrome 116+ and Node.js 18+.

Every click flies a cursor to the target and labels what it is doing. It renders inside the page, so it lands in screenshots too — you and the model look at the same picture.

✨ Why another browser bridge?

Every existing option makes you click something, every time:

| Option | What goes wrong |

|---|---|

| chrome-devtools-mcp --autoConnect | Chrome asks "Allow remote debugging?" on every connection |

| Browser MCP (store extension) | You must click the extension icon → Connect on every tab |

| WebSocket-based bridges | Open a TCP port and trust anything that can reach it |

| dsh-chrome-bridge | Nothing to click. Nothing listening on a port. |

Three things make the difference:

• 🔌 Native messaging, not a port. The extension talks to a local Node host over Chrome's native messaging pipe; the CLI reaches the host through a 0600 Unix socket guarded by a token. No TCP port to scan, no origin to spoof.
• 🎯 chrome.debugger, not injected scripts. Clicks and keystrokes are dispatched as real CDP Input.* events, so they carry a user gesture — popups open, focus works, and sites that reject synthetic events behave normally. Screenshots, network, console and raw CDP come for free.
• 👀 A cursor the human can see. A translucent light-blue arrow with a "🌐 DSH" name tag glides along a gentle arc to the target; the tag says what it is doing (click / type / drag / scroll) and each click leaves a soft ripple. It shares one style with the desktop cursor of [dsh-mac-computer-use](https://github.com/OrderG-X/dsh-mac-computer-use) (solid there, with a monitor icon), so you can tell at a glance whether the work is in the browser or on the desktop. It sits above modals and fullscreen, and picks up where it was after a navigation. Because it is rendered inside the page, it appears in screenshots.

🏗 Architecture

DSH's agent  (provided by the harness — this repo ships none)
  ├── browser_* tools  (DSH plugin)  ─┐
  └── cb CLI           (shell)       ─┤
                                      ▼
                     Unix socket  /tmp/dsh-bridge-/   (0700 dir + token)
                                      ▼
                     Node native host  ←─ native messaging (stdio) ─→  Chrome extension (MV3)
                                                                            │ chrome.debugger
                                                                            ▼
                                                                       real CDP

This repo ships no agent — the agent above is DSH's own; we only give it hands.

The extension ID is fixed by the public key embedded in plugin/vendor/extension/manifest.json, so it is identical on every machine and the native-host registration never needs editing. The Web Store build has its own store-assigned ID; the host accepts both.

🚀 Install

The host ships inside the plugin package. Adding the plugin copies the native host and the MV3 extension into place and registers native messaging for you — no git clone, no install.sh, no python3.

Requirements: macOS, Windows or Linux, Google Chrome 116+, Node.js 18+.

1. Sidebar → Plugins → Add plugin → enter this package name → Install → Enable → restart DSH:

dsh-chrome-bridge

It is an npm package. When DSH installs by package name and can't reach the official npm registry, it falls back to the npmmirror mirror in China, so GitHub is never needed. You can also paste the release tarball https://github.com/OrderG-X/dsh-chrome-bridge/releases/latest/download/dsh-chrome-bridge.tgz, which needs GitHub access.

2. The plugin installs the host on first load (~/.dsh/chrome-bridge, ~/dsh-bridge-extension, plus com.dsh.bridge.json in Chrome's NativeMessagingHosts). All that's left is getting the extension into Chrome — pick one:

Recommended: install from the Chrome Web Store — open the [DSH Bridge store page](https://chromewebstore.google.com/detail/bippcbbbipppmhjkjomgdnjbooecbimo) → Add to Chrome. No Developer mode, and the extension updates itself.

Or: load it unpacked (to run the newest extension from the repo). Chrome 137+ removed --load-extension, so that click has to be yours; the plugin walks you to it:

• the first time a browser_* tool finds nothing to talk to, it opens chrome://extensions in a background tab and puts ~/dsh-bridge-extension on your clipboard (once per session; the error text repeats the steps);
• in the file picker press ⌘⇧G, then ⌘V, then Enter — no folder hunting (Windows: paste into the picker's address bar, then Enter; Linux: Ctrl+L, paste, Enter).

Do it once, ever:

1. open chrome://extensions

2. enable Developer mode (top right)

3. Load unpacked → ⌘⇧G → ⌘V → Enter (the folder is already on your clipboard; Windows / Linux: see above)

From a source checkout, ./bridge setup does exactly this in one command: installs the host, opens the page, copies the path, and waits until the extension connects