dsh-bridge-plugin
DeepSeek Harness 插件：将本地 dsh-bridge 浏览器桥接（Python/Playwright，4 个 Web AI）作为原生 DSH 工具公开。PoC 注册 ask_deepseek；桥接本身通过 MCP stdio 复用，而非重新实现。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-bridge-plugin@0.1.2Bridge Plugin 以 dsh-bridge-plugin 发布，当前版本为 0.1.2。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Ask four web AIs from inside DeepSeek Harness — no API keys, no API bills.
dsh-bridge-plugin exposes a locally running dsh-bridge
as native DeepSeek Harness tools. It drives real, logged-in browser sessions on
DeepSeek / Doubao / Zhipu / Qwen and returns their answers — consuming free web quotas
instead of paid API tokens.
The business logic (Playwright automation, stealth, fallback chains, quality review, rate-limit state machine) stays in the Python bridge. This plugin is only a thin native shell that reuses it over MCP stdio — nothing is reimplemented.
中文说明 · Why not just MCP? · Troubleshooting
flowchart LR
A["DeepSeek Harness<br/>model + agent loop"] -->|native tool call| B["dsh-bridge-plugin<br/>this package"]
B -->|MCP over stdio| C["dsh-bridge<br/>Python + Playwright"]
C --> D["DeepSeek"] & E["Doubao"] & F["Zhipu"] & G["Qwen"]
| 🧩 Native tools | ask_deepseek appears as a first-class DSH tool — no mcp__…__ prefix |
| ♻️ One shared core | The same Python bridge the MCP integration uses; no duplicated logic |
| 🛡️ Built-in G20 guard | Refuses to send while a site is frozen, before touching the network |
| 🪶 Zero dependencies | Pure ESM JavaScript, hand-rolled MCP client, no npm deps |
| 🔍 Opt-in diagnostics | Breadcrumb logging you enable only when something misbehaves |
| 🔌 Fail-soft | A bridge problem degrades this plugin only; it never takes DSH down |
DeepSeek Harness already speaks MCP, so the MCP path needs zero code. A native plugin buys what MCP cannot:
| MCP bridge | This plugin | |
|---|---|---|
| Tool name | mcp__dshbridge__ask_deepseek | ask_deepseek |
| UI | generic MCP rendering | native presentCall card |
| Config | MCP env/args | DSH Config (Standard Schema) |
| Lifecycle | managed by the MCP client | Cordis fiber, auto-cleanup on unload/HMR |
| Requirement | Notes |
|---|---|
| DeepSeek Harness | Desktop 0.2.0-rc.2 verified; declares dsh >= 0.1.7-rc.1 |
| Node.js ≥ 20 | Provided by the DSH host itself |
| dsh-bridge | The Python project (uv managed, Python ≥ 3.11) |
| Playwright browser | uv run playwright install chromium inside dsh-bridge |
| Site logins | uv run dsh-login <site> before real-site calls |
In DSH open Settings → Plugins → Add plugin and paste the package name:
dsh-bridge-plugin
Or from a shell:
dsh plugin add dsh-bridge-plugin
Clone this repo, point the Add-plugin dialog at the folder, or use the bundled offline
installer (equivalent to dsh plugin add, plus post-install verification):
powershell -ExecutionPolicy Bypass -File install.ps1
# uninstall:
powershell -ExecutionPolicy Bypass -File install.ps1 -Uninstall
https://github.com/elysiamsia/dsh-bridge-plugin
Then fully quit and restart DSH Desktop. Closing the window may only minimize it to the tray — quit from the tray icon, or confirm no
DeepSeek Harnessprocess remains.
This package ships no machine-specific paths — its defaults assume dsh-bridge is on
your PATH (e.g. after uv tool install . in the dsh-bridge checkout).
Running from a source checkout is the common case, and that path belongs in your
profile, not in a published package. Add an override to
~/.dsh/profiles/<profile>/cordis.patch.yml:
# Replace with YOUR absolute path to the dsh-bridge checkout
- id: dsh-bridge-plugin
config:
command: uv
args: [run, --no-sync, dsh-bridge]
cwd: /absolute/path/to/dsh-bridge
toolCallTimeoutMs: 180000
A patch replaces the whole
configobject for that id, so list every field you need.
| Field | Default | Purpose |
|---|---|---|
command | dsh-bridge | Executable that starts the bridge |
args | [] | Arguments passed to command |
cwd | "" | Working directory (inherited when empty) |
env | {} | Extra environment variables |
toolCallTimeoutMs | 180000 | Per-call timeout; real-site asks drive a browser |
PYTHONIOENCODING=utf-8 and PYTHONUTF8=1 are always forced on the child process — the
bridge prints emoji, and Windows' default GBK console would crash it.
Once loaded, the model can call the tool directly:
Use ask_deepseek to explain the CAP theorem, then summarize it in two sentences.
| Tool | Parameters | Returns |
|---|---|---|
ask_deepseek | prompt (required), conversation_id (optional) | { reply, conversation_id?, site } |
dsh_bridge_probe | echo (optional) | { ok, plugin, echo? } — proves the plugin loaded |
dsh_bridge_probe is a zero-dependency diagnostic: if it works but ask_deepseek does
not, the problem is the bridge, not the plugin.
This project is built around one hard rule:
Every real-site smoke run revokes all four site accounts at once.
| Rule | |
|---|---|
| Allowed site | deepseek only, smoke tests only |
| Precondition | uv run --no-sync dsh-verify readiness must report hours_left >= 6.0 |
| Renewal | uv run --no-sync dsh-login deepseek |
The bridge's ask path does not check the rate limit itself — so this plugin adds a
pre-flight gate: before sending, it reads the verify state through the bridge's
pure-logic route_task call (no browser, no network) and refuses when the site is frozen,
returning an actionable dsh-login message. If the pre-flight check itself fails, the
plugin fails closed rather than risk sending.
Logging is off by default. Turn it on for one run:
$env:DSH_BRIDGE_PLUGIN_DIAG = "$env:TEMP\dsh-bridge-plugin.log"
The plugin then writes breadcrumbs for module import, apply entry (including the real
shape of ctx), every step, and any exception with a full stack. This is how the
"plugin loads but the tool never appears" class of bug is solved without guessing.
| Symptom | Check |
|---|---|
| Plugin row shows failed | DSH_BRIDGE_PLUGIN_DIAG — the log names the failing step |
| Plugin not listed at all | It was never installed, or DSH was not fully restarted |
| DSH crashes at startup | %APPDATA%\@deepseek-ai\dsh-desktop\logs\crash-*-host.log |
DSH reads the profile's package.json with a bare JSON.parse. A BOM makes it throw
SyntaxError: Unexpected token '' at readProfileManifest — a startup crash.
Windows PowerShell 5.1's Set-Content -Encoding UTF8 writes a BOM. Always write
BOM-less:
[System.IO.File]::WriteAllText($path, $json, (New-Object System.Text.UTF8Encoding($false)))
install.ps1 does this and asserts the result. Mind the inverse trap too: PowerShell
scripts containing non-ASCII text must have a BOM, or PS 5.1 decodes them as GBK and
fails to parse.
node probe/verify-plugin.mjs # pure + registry layers, no browser needed
# then, to also exercise the real bridge:
export DSH_BRIDGE_REPO=/path/to/dsh-bridge # PowerShell: $env:DSH_BRIDGE_REPO="..."
node probe/verify-plugin.mjs
| Script | Purpose |
|---|---|
probe/verify-plugin.mjs | Self-check: pure functions, tool registration, pre-flight gate, bridge |
probe/verify-loader.mjs | Replays the host loader's six steps against an installed profile |
probe/verify-profile.mjs | Profile health check (per bundle, detects BOM) |
probe/mcp-probe.mjs | Raw Node → Python MCP handshake + tools/list |
probe/asar-extract.mjs | Read a file out of DSH's app.asar (DSH_ASAR=…) |
Machine-specific paths are never committed: every script takes them from environment variables and tells you what to set when one is missing.
Releases are automated by .github/workflows/publish.yml,
which publishes to npm when a v* tag is pushed:
npm version patch # or minor / major — bumps package.json and creates the tag
git push --follow-tags # the tag triggers the workflow
The workflow verifies that the tag matches package.json, runs the offline self-check,
then publishes with provenance. It needs a repository secret named NPM_TOKEN — a
granular access token with "Bypass 2FA" enabled (this npm account uses 2FA; a plain
token is rejected in CI with E403). You can also trigger it manually from the Actions
tab, where the default is a --dry-run.
Issues and pull requests are welcome. Please run the self-check above before opening a PR,
and keep the zero-dependency constraint — this package must stay installable via
dsh plugin add with no build step and no transitive dependencies.