dsh-im: An IM Bot Integration Plugin for DeepSeek Harness

xmanrui/dsh-im

Integrations & ConnectionsVerified
Listed on 2026-08-20
Page last updated 2026-08-20

Connect IM bots to DeepSeek Harness via QR code or credentials, unified management for 8 channels.

Connect bots from eight IM channels like Feishu, WeChat, and DingTalk to DeepSeek Harness via QR code or credentials, with unified message handling.

install
dsh plugin --profile web add github:xmanrui/dsh-im
Category
Integrations & Connections
Platform
DSH-Plugin
Author
xmanrui
Distribution
Plugin

dsh-im Key Features

QR or credential setupUnified 8-channel managementStreaming repliesSecure local credential storage

dsh-im Repository

xmanrui
Publisher
xmanrui
Repository
xmanrui/dsh-im
76
Stars
18
Forks
0
Watchers
8
Open issues
LanguageJavaScript
LicenseMIT License
Website
Repo last push2026-08-20 03:16:36
Repo created2026-08-15 04:40:06
Topics
ai-agentschatbotcordisdeepseekdeepseek-harnessdingtalk-botdiscord-botdshdsh-pluginfeishu-botim-botslack-bottelegram-botwechat-botwhatsapp-bot
Default branchmain

dsh-im Repo Summary

dsh-im is a DeepSeek Harness (DSH) plugin for connecting IM bots, maintained by xmanrui under the MIT license, last updated in 2026-08. It solves the problem of managing multiple IM platform bots in Harness: with one plugin and one settings entry, you can connect Feishu, WeChat, DingTalk, WeCom, QQ, Telegram, Discord, and WhatsApp via QR code scanning or existing credentials. Core capabilities include QR code bot creation, credential binding, long-connection/long-polling message sending and receiving, streaming Harness responses, and independent connection supervision and session mapping for each channel.

What IM channels and connection methods does the dsh-im DSH plugin support?

Eight built-in channels, each offering QR code or manual credential entry (Telegram and Discord only manual Token, WhatsApp only QR code). Feishu supports App ID + App Secret with long connection; WeChat uses Tencent iLink long polling; DingTalk uses Client ID + Client Secret and Stream long connection with AI Card streaming; WeCom uses Bot ID + Secret and official WebSocket, natively showing "thinking" and tool execution progress; QQ uses AppID + AppSecret and WebSocket, with "typing" and streaming in private chats; Telegram and Discord use Bot Token, via Bot API long polling and Gateway v10 long connection respectively, responding only when mentioned in groups; WhatsApp scans to link device, uses WhatsApp Web long connection, shows read receipts and "typing".

How to install and configure dsh-im?

Use the following install command, then restart dsh web and open "Settings → Plugins → IM Bots" to configure. The installer automatically replaces directly installed dsh-feishu, dsh-weixin, and dsh-dingtalk in the profile, but preserves existing channel data.

bash
dsh plugin --profile web add github:xmanrui/dsh-im

You can also use npx -y github:xmanrui/dsh-im install or install from npm as @xmanrui/dsh-im. Credentials (like Secrets, Bot Tokens) are only submitted to the local Harness Host and stored in protected credential storage; the browser only receives QR codes and sanitized status.

What security and privacy designs does dsh-im have?

The plugin does not require Message Content privileged intent (Discord) and does not read unmentioned group messages; WhatsApp linked device status is stored only locally at ~/.dsh/integrations/dsh-whatsapp/auth; manually entered Secrets or Bot Tokens are submitted one-way to the local Host, and no RPC response returns sensitive information. The IM management RPC only accepts loopback browsers by default; if serving on a trusted LAN, you can explicitly open it to trusted Host authority in cordis.patch.yml.

How about local development and extensibility of dsh-im?

Local development uses npm install, npm run check, and node bin/dsh-im.mjs install --source .. npm run check runs unit tests, builds artifacts, and verifies the package contains no credentials. The plugin uses a unified channel adapter structure, so other IM platforms can be integrated following the same structure.

See more DSH plugins at dsh-plugin.org

DSH-Plugin FAQ