DSH Marketplace

dsh-im

xmanrui/dsh-im

Connect IM bots to DeepSeek Harness via QR codes or bot credentials (9 channels: Feishu, WeChat, DingTalk, WeCom, QQ, Slack, Telegram, Discord, and WhatsApp).

2,433247JavaScriptMITSource

Install

Add dsh-im to DeepSeek Harness

Install into

via npm

Resolves a published tarball rather than cloning the repository, and installs without any extra setup. Swap `web` for your profile name if you run another one.

via GitHub · npm package

Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.

What happened when we ran it

Installed cleanly when we ran it

Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run yesterdayon DeepSeek Harness 0.2.2-rc.5.

Show it in your README

install verified — dshmarketplace

For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.

Due diligence

Before you install dsh-im

  • Source of record: xmanrui/dsh-im — present in the community registry that DSH's own plugin market installs from.
  • Licensed under MIT.

Security

What installing dsh-im runs

Build scripts

No build script was blocked in our run.

Source: our sandbox install on DeepSeek Harness 0.2.2-rc.5, yesterday.

Install hooks

package.json declares no preinstall, install or postinstall script.

Source: package.json on GitHub, read at our last sync. prepare is not recorded; it runs only on a GitHub install, and shows up under build scripts when pnpm blocks it.

README mentions

Neither shell commands nor credentials.

Source: a keyword match on the README — a hint about what the plugin touches, not an analysis of its code.

Not an audit. These are the record of one install and two text scans; nobody has read this plugin's code on your behalf. Plugins run with your agent's permissions.

The AI take

What it is — Attaches DeepSeek Harness to nine messengers—Feishu, WeChat, DingTalk, WeCom, QQ, Slack, Telegram, Discord, WhatsApp—signing in with a QR code or bot credentials.

Who it is for — A DeepSeek Harness agent is already running on a machine you left behind, and the missing piece is sending it a line from WeChat or Feishu on your phone. If that agent already sits behind your own web UI or internal gateway, this hop is not what you are short on.

Watch out — On a clean profile it installed and the harness registered it; no obvious pit showed up there. Live send and receive on those nine channels was not part of that run.

The verdict — I only add it after I am willing to let this plugin hold the IM login—getting into a profile is not the decision.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

What dsh-im does

Abstract channels converge through supervised connections into isolated workspaces and session paths.

dsh-im is a DeepSeek Harness plugin that connects chat bots from multiple instant-messaging platforms to an agent through one settings page. DeepSeek Harness exposes an “IM bots” page where an operator can create or bind bots using QR codes, an App Manifest, or existing credentials. DeepSeek Harness then runs separate channel hosts, clients, RPC handlers, credential storage, connection supervision and chat-session mappings for Feishu, WeChat, DingTalk, WeCom, QQ, Slack, Telegram, Discord and WhatsApp.

The channel adapters use each platform’s documented transport: persistent connections, WebSocket, Socket Mode, Gateway, or long polling. Secrets and tokens are submitted only to the local Harness Host and stored in protected credential storage; RPC responses return redacted status rather than credentials. Each bot receives a workspace, initially set to the Host process’s process.cwd(), and supports /workspace, /workspacelist, /sessionlist and /session commands.

dsh-im suits developers who need to receive and answer Harness conversations from supported IM services without maintaining separate channel settings pages. It is a poor fit when a platform’s native bot access is unavailable or when the bot audience is not trusted: users within the platform-visible scope can run the workspace and session commands, and those commands may expose paths, session metadata or access to sessions and their available tools. WhatsApp uses a linked-device session stored under ~/.dsh/integrations/dsh-whatsapp/auth, while Telegram long polling cannot take over until an existing Webhook is removed.

dsh-im documentation

Configuring dsh-im

DeepSeek Harness provides one IM bots settings page for the nine built-in channels. QR-based setup is available for Feishu, WeChat, DingTalk, WeCom, QQ and WhatsApp. Slack uses an App Manifest plus a Bot Token (xoxb-) and App Token (xapp-); Telegram and Discord use Bot Tokens. Manually entered secrets are sent only to the local Harness Host and stored in protected credential storage. The browser receives QR codes, manifests and redacted status only.

Each bot records the Harness Host’s process.cwd() as its initial workspace. The path persists across Host restarts and can be changed from the bot card. For a Web profile exposed on a trusted local network, the README documents this optional setting:

- id: xmanrui-dsh-im
  config:
    rpcAuthority: trusted-host

trusted-host reuses Harness Host and Origin protection but does not provide user authentication.

dsh-im Commands

Command Function
/workspace <absolute path> Switches the current bot to an existing absolute directory.
/workspacelist Lists existing workspaces registered on the current Harness Host.
/sessionlist [workspace number or absolute path] Lists sessions registered for a workspace.
/session <Session ID> Binds the current chat to an existing session returned by /sessionlist.

Paths must be existing absolute directories. /session does not create or resume a session automatically; archived sessions can be bound, but child-agent sessions cannot.

How dsh-im behaves

Each bot has independent credentials, connections and session mappings. Platform replies follow channel rules: private messages generally receive replies directly, while group or server messages may require a mention or reply to the bot. New workspace mappings affect later messages; existing generated replies continue.

dsh-im access limits

Any user in the platform-visible bot scope who can message the bot may run the commands. Workspace and session data come from the global Harness Host registry and can include paths, sessions or metadata belonging to other bots or projects. A user able to bind a session may write to it or invoke its available tools. trusted-host should therefore be used only on a trusted network.

Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub

Same category

Alternatives to dsh-im

dsh-pocket

shaobeichen

2.3k

Remote phone access to the DSH Web UI: scan a QR code for LAN or public (cloudflared tunnel) access with real-time sync, a mobile-adaptive layout, and a settings tab.

Installed cleanly when we ran it

npm packageJavaScript1mo ago

AI review

dsh-pocket

What it is — Puts a phone-access tab in DSH settings that serves a LAN or cloudflared QR code so the phone can mirror and operate the desktop Web UI live.

Who it is for — The office machine is still running an agent while you are already on the commute, and you need the phone for the stream, a follow-up prompt, or an approval tap. Anyone who only drives DSH from the terminal and never starts dsh web has no surface for this plugin to attach to.

Watch out — It installed into a fresh profile in the sandbox and the harness registered it. dsh web has to be restarted before the phone-access tab shows up; turning on public access downloads cloudflared and the plugin runs shell commands locally. After a dsh web restart the phone must type the password again.

The verdict — LAN access stays enabled on my machine; the public tunnel stays down until I have actually left—keeping the full Web UI on a tunnel all day is not a trade I want.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Details
1.5k

Let your DSH agent browse Bilibili on its own, read subtitles, write a daily digest, and @ you when it finds something worth your attention.

Installed cleanly when we ran it

npm packageJavaScript8d ago

openpets

OpenPetsHQ

1.3k

Bridges DeepSeek Harness lifecycle status, errors, and approval requests to a locally running OpenPets desktop companion.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourceTypeScript1mo ago

AI review

openpets

What it is — Pushes DeepSeek Harness run state, errors, and pending approvals onto an OpenPets pet already open on the local desktop.

Who it is for — You are shipping code with a DeepSeek Harness agent on your own machine, and run state, failures, and approval prompts only flicker inside the session, so you want a desktop pet to catch them. Skip it when DSH lives on a headless remote host; nothing on that box can receive the events.

Watch out — There is no one-command package; you have to attach it as a subdirectory plugin from the repository. It invokes the system shell at runtime.

The verdict — I would not treat it as an agent feature; it does not change how I approve work, only whether I catch the prompt in peripheral vision.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

Connects DeepSeek Harness to Avernet's Bot Collaboration Network over WebSocket V2, with automatic onboarding, isolated agent sessions, tool-call events, and multi-bot routing tools.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourcePython1mo ago

AI review

deepseek-harness-channel-bcn

What it is — This plugin connects DeepSeek Harness to Avernet's Bot Collaboration Network.

Who it is for — When you need to run multi-agent collaboration tasks with DeepSeek Harness. If your work involves only independent agents without needing the Bot Collaboration Network, you can use other approaches.

Watch out — Sandbox testing has not been performed. Static check indicates it will execute shell commands. No obvious issues found.

The verdict — I would install it if I need Avernet infrastructure integration, because it supports WebSocket V2 connection.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

dsh-qqbot

zaofan-make

225

QQ official bot channel (enhanced fork of tencent-connect/dsh-qqbot): full agent chat in groups and DMs, rich media, an auto-tagged sticker library with AI image replies, join approval, mute and broadcast, scheduled wakeups, remote approvals over QQ, interactive cards, multi-account instances, extensions, member profiles, and token-saving value-scored wakeups.

Installed cleanly when we ran it

npm packageTypeScript15d ago

dsh-deepcanary

Oscar-Williams

182

Evidence-first attention supervision for DeepSeek Harness with C0–C3 policy, deduplicated Inbox alerts, quiet hours, and redacted outcome records.

Installed cleanly when we ran it

npm packageTypeScript16d ago