dsh-codex-chrome

English · 简体中文

Control your own Chrome from DeepSeek Harness by migrating OpenAI Codex's chrome@openai-bundled plugin into DSH. The agent gets a set of native mcp__chrome__* tools and can reuse the browser state you already have — open tabs, cookies, logged-in sessions — to navigate, read pages, click, type and take screenshots.

Above: a DSH session calling chrome_observe { mode: "screenshot", fullPage: true } and getting a capture of the page open in the user's own Chrome.

What the Codex "plugin" actually is

It is enabled in ~/.codex/config.toml as:

[plugins."chrome@openai-bundled"]
enabled = true

But it is not an MCP server. It is three things:

browser-client.mjs drives the work through globalThis.nodeRepl.rpc("browser", …), and that service only runs inside the Codex node_repl host: it depends on privileged capabilities that exist nowhere else (nativePipe, addTurnEndedHandler, createElicitation, host-injected turn metadata). This migration therefore does not rewrite browser control — it reuses the vendor runtime exactly as shipped.

Why there is an extra bridge process

Every browser call must carry Codex turn metadata:

{ "_meta": { "x-codex-turn-metadata": { "session_id": "…", "turn_id": "…", "call_id": "…" } } }

The browser service reads it from nodeRepl.requestMeta and hard-fails without it:

Missing required Codex turn metadata: session_id, turn_id

@deepseek-ai/dsh-mcp-client has no per-call _meta support — its only call site is client.callTool({ name, arguments }, { … }) — so bin/chrome-mcp.mjs fronts node_repl, injects the metadata, and republishes the browser API as native DSH tools:

DSH ──mcp-client(stdio)──▶ bin/chrome-mcp.mjs ──MCP(stdio) + _meta──▶ Codex node_repl
                                  │                                        │
                                  │                             trusted service browser-service.mjs
                                  │                                        │
                                  └────────── native tools ◀────── ChatGPT browser extension ◀▶ Chrome

Install

DSH Desktop

Open the plugin manager and install the bundle from this directory, or from a registry once published. Desktop profiles are managed exclusively by the app, so dsh plugin --profile desktop add … is refused by design.

CLI profiles

dsh plugin --profile web add /absolute/path/to/dsh-codex-chrome

Either way the profile's package.json ends up with the dependency and the bundle entry; doing it by hand is equivalent:

"dependencies": { "dsh-codex-chrome": "link:/path/to/dsh-codex-chrome" }
"dsh": { "profile": { "bundles": [ "…", "dsh-codex-chrome" ] } }

then run pnpm install in the profile directory. After a restart the model sees the eleven mcp__chrome__* tools and the control-chrome skill.

Tools

The model-facing workflow, documented in the bundled control-chrome skill, is observe → act → observe: prefer accessibility element indices over coordinates, and re-derive the indices after every action.

Implementation notes

• State lives on globalThis, not in module scope. Every js call in node_repl is evaluated in a fresh realm that re-evaluates the same import(); module-level bindings reset, while globalThis is shared for the life of the kernel.
• Screenshots cannot be written to disk. Once the browser service is active the kernel filesystem turns read-only (even /tmp and $CODEX_HOME return EROFS), so images go out through nodeRepl.emitImage; the bridge spools a copy on the host side.
• Accessibility indices are bound to the call that produced them. chrome_act re-reads tab.ax.get("state") before acting so an index returned by chrome_observe is usable.
• The _meta injection is the whole point. Without it every browser call fails.
• The vendor capture path labels JPEG as PNG. Both the sandbox and the bridge re-derive the type from magic bytes, because DSH rejects an image whose declared type disagrees with its payload.

Self-checks

node scripts/check-package.mjs   # static package consistency, no browser needed
node --test                      # 13 tests: unit checks + a real MCP handshake
node scripts/doctor.mjs          # assets, extension, native host, node_repl
node scripts/doctor.mjs --deep   # …plus one real browser round trip
node scripts/smoke.mjs           # end to end: open a tab, observe, screenshot, evaluate, close

Requirements

• Linux (developed and verified on Arch with Chrome 154, on both Wayland and X11).
• The ChatGPT/Codex desktop app must have run at least once, so it materialises ~/.codex/plugins/cache/openai-bundled/{chrome,browser}/… (scripts/browser-client.mjs, browser-service.mjs, extension-host).
• The ChatGPT browser extension installed in the target browser, with the com.openai.codexextension native messaging host registered (~/.config/google-chrome/NativeMessagingHosts/).
• The target browser running.

Environment overrides:

Licence and provenance

This package is MIT licensed. It ships no OpenAI code: it calls browser-client.mjs / browser-service.mjs from your local Codex installation at runtime, and those proprietary files are not redistributed. See THIRD_PARTY.md.