Connect IM tools to DeepSeek Harness: DSH plugin setup

DeepSeek Harness connects to IM tools through instant-messaging DSH plugins - they route conversations and notifications into channels such as Feishu, WeChat, and DingTalk; for example, dsh-im supports bots on nine channels and unifies the management of multiple bot connections (source). This guide covers what these plugins do, how to configure credentials and profiles, how to triage when messages will not flow, and how to disable and uninstall them.

DSH plugin overview: the three layers of IM integration

What an IM integration plugin does is build a channel between DeepSeek Harness and an IM platform. Lay out the three layers first:

In one sentence: the IM platform must allow it, the plugin must connect, and the framework must load it - miss any one and nothing flows.

What DSH plugin IM integration can do: move conversations and notifications into instant messaging

Its value is bringing DeepSeek Harness's capabilities into the IM you already use, rather than making you spin up another system. Main capabilities:

1. Multi-channel routing - one plugin manages multiple bots across several IM channels (source). Expected: no need to install a separate set for each channel.
2. QR-code or credential onboarding - two configuration methods are supported, lowering the bar for filling in parameters. Expected: pick whichever is less trouble given what you have on hand.
3. Unified connection management - connection status for multiple bots is viewed in one place. Expected: a broken one is visible at a glance.

Keep this distinct from "connecting to a specific external tool": Connect workbuddy covers hooking up one particular external tool, whereas IM integration here is the general configuration for "instant messaging as a category" - different subjects.

DSH plugin configuration path: install the plugin, enter credentials, set profile and permissions

Configuration has four steps: choose a channel -> install the plugin -> enter credentials / webhook -> set the profile and restart. The steps:

1. Prepare the bot on the IM platform side - create a bot or app on the matching platform and obtain the Bot Token, app secret, or webhook. Expected: usable onboarding credentials in hand, with send/receive permission enabled.

2. Install the integration plugin - go to the DSH Plugin Hub and search by keywords such as IM, instant messaging, or bot, or run:

   bash

   dsh plugin --profile web add @xmanrui/dsh-im
   

   Expected: the plugin enters the web profile, with no install errors.

3. Enter credentials / webhook - open the plugin configuration and enter the credentials from the previous step per channel; channels that support QR codes can be scanned directly. Expected: the configuration saves, and is written to a credentials file rather than scattered in plaintext.

4. Confirm profile and permissions - make sure it is installed in the profile you are actually using, and verify the permissions the bot needs are granted. Expected: the plugin is compatible with the host version and has sufficient permissions.

5. Restart to take effect and self-test - restart dsh web and send a message to the bot in the IM. Expected: a reply arrives, confirming the link is up.

The semantics of --profile web are straightforward: whichever profile you install into, only that environment is affected (source). With multiple profiles, always confirm you installed into the right one.

DSH plugin common problems and disabling / uninstalling

When messages will not flow, check in order; to disable, stop the connection first and then uninstall. Triage and cleanup steps:

1. Is the plugin loaded - go to the installed list and confirm the plugin is there, and that the service has been restarted. Expected: the plugin appears in the list with no parse errors in the startup log.
2. Is the credential valid - verify the Token / secret is not expired or mistyped, and whether the webhook was reset by the platform. Expected: sending and receiving work after switching to a valid credential.
3. Is the network reachable - confirm this machine can reach the matching IM's open API and that a proxy is not blocking requests. Expected: connectivity is normal.
4. Is permission granted - check whether the bot has been granted permission to send and receive messages on the IM side. Expected: messages get through once the permission is granted.
5. When you want to disable / uninstall - first turn off the connection in the plugin configuration, then uninstall from the installed list, then restart. Expected: the plugin is removed and its UI entry disappears; then disable the bot or webhook on the IM side to avoid leftover pushes.

IM integration is, at heart, still installing and managing plugins - rather than hunting for packages and memorizing commands across multiple repositories, use a plugin market to download and manage them in one place: DeepSeek Harness's DSH Plugin Hub puts browsing, one-click install, uninstall, update detection, and system logs together, with a confirmation dialog before every install and centralized management in the installed list afterward.

DSH plugin notes

These are the DSH plugin points to remember before connecting IM. Item by item:

1. Treat credentials like passwords: only enter Bot Tokens and webhooks into trusted plugins, and never paste them into chat or public repositories.
2. Align the profile: installing into the wrong profile is a frequent cause of "installed but not working."
3. Least privilege: grant only the permissions needed to send and receive messages, not everything.
4. Restart to take effect: configuration and plugin changes load after a restart.
5. Finish the cleanup: after uninstalling the plugin, delete the bot on the IM side, disable the webhook, and revoke old Tokens.

Sources: dsh-im (dsh-plugin.org), dsh CLI README, dshplugin/dsh-plugin-hub