Blog · Guide
Put DeepSeek Harness inside your IM — WeChat, QQ, Feishu, DingTalk & Telegram
August 16, 2026 · dshbase
DeepSeek Harness runs as a local web app at 127.0.0.1:3080 — but a large and loud part of its community has no interest in keeping a browser tab open. They want the agent to reach them where they already live: WeChat, QQ, 企业微信, 飞书, 钉钉, Telegram. The plugin ecosystem has answered with a fast-growing pile of IM bridges, and it's one of the most active corners of the official discussions (#1458, #1689, #2303). Here's the current lineup.
Why IM bridges are the killer use case
For 国内 users, the chat app is the operating system. Run dsh headless on a home server or a spare box, bolt on an IM bridge, and you get a 24/7 agent reachable from your phone — no port forwarding, no browser, no SSH. The same pattern that made ClawBot-style QR-login bridges popular overnight. It's the natural pairing of dsh's --headless mode with the one surface people never close.
WeChat (微信)
The busiest category, and the one with the most caveats — WeChat has no official bot API, so every bridge is either a personal-account QR login or a webhook relay:
- DeepSeek-harness-weixin — ClawBot-style QR login that binds your personal account as the agent.
- dsh-plugin-wechat — the earliest general-purpose WeChat adapter.
- dsh-wechat-maid — a "personal maid" bot with session memory per contact.
- dsh2wechat and dsh-wechat-notify — push notifications / one-way relays from dsh to WeChat.
QQ is friendlier than WeChat for bots because of the OneBot protocol, which the ecosystem has standardized on:
- dsh-qqbot — the main QQ bridge.
- DeepSeek-harness-qqbot — a parallel, actively-maintained implementation.
- dsh-onebot — speaks OneBot, so it works with most QQ bot frameworks, not just one client.
企业微信 (WeCom) & 钉钉 (DingTalk)
These two matter because they're the "official-looking" channels — WeCom and DingTalk both expose a proper bot/webhook API, so these bridges don't fight the platform the way WeChat bridges do:
- DeepSeek-harness-wecom, dsh-wecom, dsh-WeCom-notify — WeCom bots and notify relays.
- DeepSeek-harness-dingtalk — the DingTalk bridge.
- dsh-notify — a multi-channel notifier covering ServerChan, 钉钉, 飞书 and plain webhooks in one plugin.
飞书 / Lark
Feishu is the most bot-native of the bunch — real webhook events, no QR login required. The standout is dsh-adapter-feishu, which connects over WebSocket so it needs no public IP — you can run it from a NAT'd home machine. Around it: dsh-lark, dsh-lark-bot, dsh-feishu, dsh-feishu-bot.
Telegram & multi-platform
- telegram (by LoserFox) — the Telegram bridge.
- dsh-im-hub — a hub that fans one agent out to several platforms at once.
- plugin-notify — webhook notifications to 飞书 / 企微 / 钉钉 / Slack / Discord.
- dsh-im-gateway and dsh-im-bridge — generic gateway/bridge scaffolding for building your own adapter.
Install reality check
Most of these are early and install-from-source — a large share are marked not-on-npm in the directory, so expect to clone a repo and dsh plugin add ./path rather than a clean dsh plugin add name. The QR-login WeChat bridges, in particular, sit in a gray area with WeChat's risk-control and can get a personal account flagged — treat them as experimental, use a throwaway account, and prefer the webhook channels (Feishu / WeCom / DingTalk / Telegram) for anything you need to keep running unattended. Every detail page carries a test badge and an exact install command, so check before you commit.
Before you build your own
The gap between "I want my agent in WeChat" and "there's a plugin for that" is shrinking weekly. Search the plugin directory by platform before writing a new bridge — the OneBot, WebSocket-Feishu and webhook patterns are already solved, and you'll almost always be better off extending an existing adapter than starting from scratch.