MIT-licensed DeepSeek Harness plugin that extends your local dsh session to phones (LAN QR), public tunnels (Cloudflare / self-hosted) and IM bots (WeChat / QQ / Feishu / Telegram), with PBKDF2 access auth, console tamper-lock and never-self-lock recovery.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-08-29
License
MIT
01What can it help you accomplish?
Remotely continue a DeepSeek Harness session from a phone, tablet or the public internet
A scanned-QR LAN bridge plus Cloudflare / self-hosted tunnels that expose the DSH web UI on any device — no self-hosted public server needed
DeepSeek Harness (dsh) users who want to keep talking to their agent away from the desk, across networks, or from a mobile device
Drive DeepSeek Harness through WeChat / QQ / Feishu / Telegram bots
IM chatbots that relay prompts, media and approval requests to your agent, with multi-workspace selection and sessions persisted across restarts
Teams and individuals who live in WeChat / QQ / Feishu / Telegram and want to invoke their DSH agent without opening the desktop app
02How to install into DeepSeek Harness
Prerequisites
- Node.js ≥ 22 — the README requires `^22.19.0` or `≥ 24.0.0`
- `dsh` CLI available — you must be able to run `dsh` in the terminal
Installation steps
- 01
Install from npm: `dsh plugin --profile web add @wenbin_wb/dsh-bridge`
$ dsh plugin --profile web add @wenbin_wb/dsh-bridge
- 02
Or from source: `git clone https://github.com/wenbin-wb/dsh-bridge.git` then `dsh plugin --profile web add ./dsh-bridge`
$ git clone https://github.com/wenbin-wb/dsh-bridge.git
- 03
Restart DSH; open Settings → Remote Access to start using it
Verify the integration
Not specified by the author
03DSH integration and capability boundaries
Installed as a native DeepSeek Harness plugin via `dsh plugin --profile web add`; runs inside the DSH web profile and adds remote-access & IM-bot channels.
LAN QR-code bridge
a phone/tablet on the same Wi-Fi→direct access to the DSH web UI by scanning the on-screen QR code — zero config
Cloudflare tunnel (public URL)
one click in Settings → Remote Access→a public `https://*.trycloudflare.com` URL, or a fixed Token-domain tunnel that auto-starts with DSH
Self-hosted tunnel
a server with a public IP running the tunnel server→a fixed domain over WebSocket (`wss://…`) with config persisted across restarts
WeChat bot (ClawBot / iLink)
a personal WeChat account scanned in→chat, control and approval of the DSH agent inside WeChat — multi-workspace, persisted sessions, media
credentials stored in the DSH credential service, not in plaintext configQQ bot (OpenAPI v2)
QQ bot AppID + ClientSecret→1:1 / group chat relay with Markdown, buttons and rich media
Feishu bot (WebSocket)
Feishu enterprise self-built app App ID + Secret→chat relay over the official WebSocket — no public IP, with Card 2.0 approval buttons
Telegram bot (Bot API + proxy)
Telegram Bot Token (optional HTTP/HTTPS proxy)→chat relay via official Long Polling — no public IP, with inline approval cards
Access auth & tamper protection
enable in Settings → Remote Access → Security→external access gate, admin-lock console, 3-tier disaster recovery that can never self-lock
core system path blacklist blocks `C:\Windows\System32`, `/etc/shadow`, `/root/.ssh`
04Who is it for? When not to use it?
Good for
- DeepSeek Harness (dsh) users who want to keep talking to their agent away from the desk, across networks, or from a mobile device
- Teams and individuals who live in WeChat / QQ / Feishu / Telegram and want to invoke their DSH agent without opening the desktop app
Not for
- Requires Node.js ≥ 22 (DSH requires `^22.19.0` or `≥ 24.0.0`); older runtimes are unsupported.
05Compatibility, maintenance and safety notes
- Requires Node.js ≥ 22 (DSH requires `^22.19.0` or `≥ 24.0.0`); older runtimes are unsupported.
- WeChat bot uses an iLink exclusive lock — only one bot may poll a WeChat account at a time; use a dedicated account or it will 403-conflict with hermes-agent / OpenClaw.
- Right after a release, `add @latest` may still install the old version because pnpm 11's `minimumReleaseAge` filters releases younger than 24h; wait or set `minimumReleaseAge: 0`.
- QQ / Feishu / Telegram bots rely on their vendors' realtime WebSocket/polling APIs, so the host must reach the public internet; LAN QR bridging and the WeChat (iLink) path need only the local network.
MIT · actively maintained (latest release v2.8.5, 2026-08-27)
06Frequently asked questions
How do I connect dsh-bridge to DeepSeek Harness?
Install the official dsh CLI (Node.js ≥ 22, `^22.19.0` or `≥ 24.0.0`), then run `dsh plugin --profile web add @wenbin_wb/dsh-bridge` (or `npx --yes @deepseek-ai/dsh plugin --profile web add @wenbin_wb/dsh-bridge` without global rights). Restart DSH and open Settings → Remote Access.
After scanning the QR code or using a public tunnel, can outsiders reach my DSH console?
Only if you don't enable auth. In Settings → Remote Access → Security you can turn on a global password or security Token gate; visitors must then authenticate. The host machine (`127.0.0.1`) keeps physical privilege and auto-passes without a password, so local desktop use is unaffected.
How are WeChat / QQ / Feishu / Telegram bot messages kept safe?
A strict allowlist is enforced — only whitelisted senders drive the agent; everyone else's messages are silently dropped and never fed to the LLM. Admins are auto-whitelisted on first message, and approval requests auto-deny after the timeout if not answered.
What's the difference between a Cloudflare temp tunnel and a fixed-domain (Token) tunnel?
The temp mode (default) needs no Cloudflare account and gives a random `https://*.trycloudflare.com` URL — great for quick outings. The Token mode binds your own domain (e.g. `dsh.yourdomain.com`) via a Named Tunnel Token and keeps the URL fixed across DSH restarts when auto-start is on.
After upgrading the plugin or restarting DSH, do my chats and bot configs disappear?
No. All IM credentials, allowlists, tunnel auto-start options and auth rules live in the local `~/.dsh/dsh-bridge/` directory, surviving upgrades and restarts. Sessions are persisted by the DSH core engine and resume via `/resume`. You can also one-click export a `.json` backup for migration.
07Related DSH workflows
awesome-gpt-image-2
by freestylefly
Prompt-as-Code engine and template library for GPT-Image2, with 470+ reverse-engineered cases, 20+ production templates and distilled agent skills.
voyager
by nagi-ovo
Browser extension that enhances Gemini, AI Studio, Claude and ChatGPT with a prompt manager that works across any web UI, DeepSeek Harness included.
dsh-im
by xmanrui
把 IM 机器人接入 DSH：统一管理飞书/微信/钉钉/企业微信/QQ/Telegram/Discord/WhatsApp 八个渠道，扫码或凭据接入、流式回复与设置页管理
chatgpt-gemini-timeline
by houyanchao
Chrome extension that adds folders, a prompt library, and a conversation timeline to ChatGPT & Gemini chat pages — works alongside DeepSeek Harness.
08Data and sources
dsh plugin --profile web add @wenbin_wb/dsh-bridge
安装完成后重启 DSH，在设置页找到「远程访问」即可使用。
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-08-29. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.