Back to directory

dsh-channels

In a curated listMaintenance: Active

wsz987/dsh-channels

Connect five IM platforms to DSH with QR/bot authentication, unified channel sessions, rich messages, and attachment handling.

View on GitHub
$ npx @deepseek-ai/dsh plugin --profile web add -w @wsz987/dsh-channels@latest

15

stars

3

forks

TypeScript

Language

MIT

License

2026-08-13

Created

2026-09-11

Last push

MIT-licensed DSH plugin bundle that connects WeChat, QQ, DingTalk, Feishu and Telegram to DeepSeek Harness with unified configuration, QR/bot authorisation, attachment extraction and the host's official slash commands available inside every chat.

DSH integration

Native runtime

Author-claimed

Safety audit

Unaudited

Last verified

2026-11-14

License

MIT

01What can it help you accomplish?

  • Talk to your DSH agent from the IM apps you already use instead of the Harness window

    One agent reachable from WeChat, QQ, DingTalk, Feishu and Telegram, all configured and QR-authorised from a single 「设置 → 渠道」 panel

    People who want DeepSeek Harness answers inside the chat app they keep open on the phone and desktop

  • Send screenshots, PDFs, spreadsheets and documents to the agent from a chat

    Images read directly by vision-capable models, and PDF / DOCX / XLSX / text attachments extracted so the agent can read them (100 MiB per inbound file)

    Analysts and support staff who receive files in chat and want the agent to work on them in place

  • Control a running DSH session from inside the chat

    The host's official slash commands work in any channel session — `/stop`, `/new`, `/help`, `/status`, `/version`, `/models`, `/model`, `/mirror` and `/bind`

    Users who start a long agent task from their phone and need to inspect, stop or re-bind the session without opening the Harness UI

02How to install into DeepSeek Harness

Prerequisites

  • `npx @deepseek-ai/dsh` runs, and a normal session in Harness Web can hold a conversation
  • DeepSeek Harness `0.1.5-rc.2` and Node `22.19+` (the README points at docs/compatibility-matrix.md for the version table)
  • Per-channel platform credentials — a QQ AppID/AppSecret, a DingTalk clientId/clientSecret, a Feishu AppId/AppSecret, or a Telegram Bot Token; WeChat needs none and is QR-logged-in

Installation steps

  1. 01

    Install the stable bundle: `npx @deepseek-ai/dsh plugin --profile web add -w @wsz987/dsh-channels@latest`

    $ npx @deepseek-ai/dsh plugin --profile web add -w @wsz987/dsh-channels@latest

  2. 02

    Check the bundle was merged into the profile: `npx @deepseek-ai/dsh --profile web --dump-config`

    $ npx @deepseek-ai/dsh --profile web --dump-config

  3. 03

    Start Harness Web: `npx @deepseek-ai/dsh web`

    $ npx @deepseek-ai/dsh web

  4. 04

    In Harness Web open 「设置 → 渠道」 to configure or log into the channels you need, then finish the 「安全访问」 (secure access) setup

  5. 05

    Keep the `-w` flag on install, update and removal; when upgrading, raise Harness first and update the plugin after

Verify the integration

  • `npx @deepseek-ai/dsh --profile web --dump-config` shows the bundle merged into the profile
  • In 「设置 → 渠道 → 安全访问」 confirm who may use the local agent through the bot — until that is confirmed a channel can look connected while messages never reach the agent

Rollback

  • `npx @deepseek-ai/dsh plugin --profile web remove -w @wsz987/dsh-channels`

03DSH integration and capability boundaries

DSH integrationNative runtime

DSH plugin bundle installed into a profile with `dsh plugin --profile web add -w`, configured from the Harness Web 「设置 → 渠道」 panel

  • Five channel adapters behind one panel

    channel credentials or a QR login per platform (WeChat needs none; QQ, DingTalk, Feishu and Telegram need app credentials or a bot token)→a live session per channel account, with text, image and file support (WeChat inbound files only) and streaming replies on QQ / DingTalk / Feishu / Telegram

    WeChat credentials are persisted automatically after the QR loginstarting a Telegram bot calls `deleteWebhook` to remove any webhook already configured for that bot
  • Inbound access control

    the 「设置 → 渠道 → 安全访问」 settings: identify my account, per-group allowlists or an explicit 「所有群组」 switch→an allowlist of accounts and groups that may drive the local agent; anyone else's messages never reach it

    group chat is off by default and each allowed group must be added manually
  • Attachment extraction

    images, PDF / DOCX / XLSX / text attachments sent into a channel session (100 MiB per inbound file)→images for vision-capable models, and extracted text from documents so the agent can read them

    audio and video are only degraded handling, not full support
  • Official slash commands inside chat

    a slash command typed in any channel session→the host command system executes it — `/stop`, `/new`, `/help`, `/status`, `/version`, `/models`, `/model`, `/mirror`, `/bind`; unknown commands are rejected instead of being sent to the model

    `/stop` cancels the current agent immediately, ahead of queued channel messages`/model` also writes the global default model for later new sessions
  • Per channel-account workspace isolation

    the `workspace.mode` config in `$DSH_HOME/profiles/web/cordis.patch.yml`→each channel account gets its own isolated workspace by default; `host-cwd` or `disabled` are the alternatives

    editing the patch file is the only way to change the isolation mode

04Who is it for? When not to use it?

Good for

  • People who want DeepSeek Harness answers inside the chat app they keep open on the phone and desktop
  • Analysts and support staff who receive files in chat and want the agent to work on them in place
  • Users who start a long agent task from their phone and need to inspect, stop or re-bind the session without opening the Harness UI

Not for

  • Needs DeepSeek Harness `0.1.5-rc.2` and Node `22.19+`; the plugin must match the Harness version, so upgrades go Harness first and plugin second, with the `-w` flag kept on every install, update and remove.
  • Messages from people who are not on the secure-access allowlist never reach the agent, and a channel can display as connected while that is the case. Group chat is closed by default. Channel sessions normally run `Workspace Write` — `Full access` only when you really need files outside the workspace and trust the task.
  • Per-channel feature gaps: WeChat only reads inbound files (no file sending, no streaming replies) and audio / video are degraded everywhere. Telegram needs Bot API 10.2+ and long polling only, and it removes the bot's existing webhook on start, so the same bot must not serve another webhook consumer.
  • The project iterates quickly and the README asks you to back up your data before upgrading; it is a community extension, not an official DeepSeek Harness or messaging-platform project.

05Compatibility, maintenance and safety notes

  • Needs DeepSeek Harness `0.1.5-rc.2` and Node `22.19+`; the plugin must match the Harness version, so upgrades go Harness first and plugin second, with the `-w` flag kept on every install, update and remove.
  • Messages from people who are not on the secure-access allowlist never reach the agent, and a channel can display as connected while that is the case. Group chat is closed by default. Channel sessions normally run `Workspace Write` — `Full access` only when you really need files outside the workspace and trust the task.
  • Per-channel feature gaps: WeChat only reads inbound files (no file sending, no streaming replies) and audio / video are degraded everywhere. Telegram needs Bot API 10.2+ and long polling only, and it removes the bot's existing webhook on start, so the same bot must not serve another webhook consumer.
  • The project iterates quickly and the README asks you to back up your data before upgrading; it is a community extension, not an official DeepSeek Harness or messaging-platform project.
2026-08-132026-09-11v0.5.1

MIT · README evidence only, latest release v0.5.1, no security audit

06Frequently asked questions

How do I install dsh-channels into DeepSeek Harness?

Run `npx @deepseek-ai/dsh plugin --profile web add -w @wsz987/dsh-channels@latest`, confirm with `npx @deepseek-ai/dsh --profile web --dump-config`, then start Harness Web with `npx @deepseek-ai/dsh web`. Keep the `-w` flag on install, update and remove.

Which versions does it require, and in what order do I upgrade?

The README names DeepSeek Harness `0.1.5-rc.2` and Node `22.19+`, with a compatibility matrix in the repo. Plugin and Harness must match, so upgrade Harness first (`npm i -g @deepseek-ai/dsh@next`) and update the plugin afterwards — `update` within the same version line, `add` again when crossing lines.

Why does a channel show as connected but the agent never answers?

Secure access has not been confirmed. In 「设置 → 渠道 → 安全访问」 verify who may use the local agent through the bot — the plugin does not treat anyone who can message the bot as authorised. WeChat uses the scanned account automatically; DingTalk / Feishu / Telegram need 「识别我的账号」 with a DM to the bot; QQ private chat works for the creator only and groups are configured separately.

What can I send through a channel?

Text everywhere, images both ways, files on QQ / DingTalk / Feishu / Telegram. Vision-capable models read images directly and PDF / DOCX / XLSX / text attachments are extracted for the agent, up to 100 MiB per inbound file; WeChat only reads inbound files, audio and video are degraded, and streaming replies are not available on WeChat.

Can I control a running session from the chat?

Yes — the host's official command system parses slash commands in any channel session: `/stop` cancels the current agent immediately ahead of queued messages, `/new`, `/help`, `/status`, `/version`, `/models`, `/model`, `/mirror` and `/bind`. Unrecognised slash commands get 「未知命令」 and are not sent to the model, and some commands are unavailable in group chats.

08Data and sources

  • Author-claimedgithub.com8401caaa340c…

    将微信、QQ、钉钉、飞书和 Telegram 接入 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness)

  • Author-claimedgithub.com8401caaa340c…

    接入后,在 Harness Web“设置 → 渠道”面板统一配置与扫码授权,并在各平台对话框中直接与 Agent 对话(图片来源:[docs/ScreenShot](./docs/ScreenShot)):

  • Author-claimedgithub.com8401caaa340c…

    npx @deepseek-ai/dsh plugin --profile web add -w @wsz987/dsh-channels@latest

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-14. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.