Notifications & Integrations

What it is — dsh-im plugin for connecting IM bots to DeepSeek Harness via QR codes or bot credentials, supporting nine channels and enabling local Harness to connect to public AI Office.

Who it is for — When users need to handle AI Office tasks in enterprise IM such as WeChat or DingTalk and require Harness to connect outward it is suitable to install. It allows multiple bots per IM channel with independent binding of status, workspace and model. Not suitable for users who only run locally with no public network requirement.

Watch out — Tested successfully registered and enabled in a fresh profile with no obvious installation or usage issues found.

The verdict — I would install it because it solves the IM access pain point for Harness connecting to public AI Office without extra configuration.

What it is — dsh-pocket enables remote phone access to the DSH Web UI via QR code scan for LAN or public cloudflared tunnel with real-time sync.

Who it is for — When you are away from your desk and want to monitor an agent task running on your computer, this plugin is suitable. Users in advanced mode on the desktop version may find it inapplicable as mobile access is temporarily unsupported.

Watch out — Sandbox testing passed in a fresh profile. The plugin installs with a single npm command. Session persistence requires the dsh web process to remain active, and public access requires agreeing to the disclaimer.

The verdict — I would install it because it provides real-time mobile access to the web UI, but only if the dsh web process stays running to maintain the session.

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

Who it is for — Users who want to bridge DeepSeek Harness lifecycle status, errors, and approval requests to a local OpenPets desktop companion can install this plugin. Users who do not run local OpenPets desktop companion can skip this plugin.

Watch out — Not sandbox tested. Static check indicates it will execute shell commands.

The verdict — I would install it if bridging to local OpenPets is needed, because it connects lifecycle status and errors directly.

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.

What it is — Sends notifications via IM webhooks and local systems when turns complete, errors occur, or approvals are pending.

Who it is for — When using DeepSeek Harness for turn completion, errors, or approval notifications, users needing instant results should install this plugin. If not involving external IM integration, users can skip this plugin.

Watch out — This is a subdirectory plugin with no single command install. Manual allowance of shell script execution is required from source builds. It executes shell commands and requires API key or token. No sandbox testing was conducted.

The verdict — I would install it because it handles notifications for turn completion and errors in agent workflows, but only if external IM integration is necessary.

What it is — DeepSeek Harness Lark/Feishu plugin: integrates chats to drive agents with card-based approvals.

Who it is for — Users collaborating multiple DeepSeek Harness agents in one Lark/Feishu group chat benefit from independent sessions and turn handoff. Users who do not use Lark or Feishu as integration channels can skip this plugin because they lack the chat environment.

Watch out — No public server or callback configuration needed. Tested and registered successfully in a new profile. No obvious issues found.

The verdict — I would install it because no public server or callback configuration is required.

What it is — dsh-notifier plugin for DeepSeek Harness adds a single notify() API across 27 notification channels with event-driven pushes and phone approvals.

Who it is for — It suits users who run DeepSeek Harness agents that require multi-channel notifications and mobile approval workflows. Users without multi-channel or mobile interaction needs do not need it.

Watch out — Sandbox testing confirms it installs and registers successfully in a fresh profile. Zero runtime dependencies. No obvious issues found. It may execute shell commands, but this is a static check note, not a runtime defect.

The verdict — I would not install it because it requires manual approval for build scripts and its scope is limited to notification and control rather than core agent functionality.

What it is — dsh-lark-bot bridges DeepSeek Harness into Feishu/Lark bot, enabling chat-based control of local coding agents with streaming cards, multi-role agents, workspaces, and safety net.

Who it is for — Developers who use Feishu/Lark for team collaboration in group chats or topics can install it. Those who run DeepSeek Harness exclusively via terminal do not need it, as they have no requirement for Feishu integration.

Watch out — The plugin executes shell commands. Sandbox testing confirmed successful registration in a new profile. No obvious issues found.

The verdict — I would install it because it provides safety-net guardian for crashed DSH instances, which is a relevant value in Feishu workflows.

What it is — dsh-lark-link is a Feishu/Lark bridge plugin for DeepSeek Harness. It supports QR one-click auth, card-based commands, intent-confirmation cards, zero-loss messaging, and media in/out.

Who it is for — If you need to communicate with your DeepSeek Harness agent in Feishu group chats and manage tasks on mobile without staying at the terminal, this plugin fits your needs. Users who operate solely within the terminal and do not require media input/output or group chat integration do not need to install it.

Watch out — It requires an API key or token to be provided. Sandbox testing confirmed it registers successfully in a new profile. It will execute shell commands. No obvious issues were found.

The verdict — I would install it because it enables the agent to land sessions in the correct workspace via a reusable DSH Web GUI. This is useful if workspace management is important.

What it is — It is an ACP profile plugin and standalone server for DeepSeek Harness.

Who it is for — Users who want to use the DeepSeek Harness agent from Zed via the ACP protocol are suitable to install it. Users who do not use Zed or other ACP clients can manage credentials and sessions directly in the DeepSeek Harness web interface.

Watch out — After installation in a new profile, it is registered by the harness and executes shell commands. Sandbox testing passed with no obvious pitfalls found.

The verdict — I would not install it because it only serves as a bridge for specific client integrations without changing the core capabilities of the DeepSeek Harness agent.

What it is — This plugin provides a Feishu interface control console for DeepSeek Harness.

Who it is for — Users who need to access commands and handle approvals via panel in Feishu chats with DeepSeek Harness agents are suitable to install this plugin. If you primarily use DeepSeek Harness in terminal or web environments, you do not need to install this plugin.

Watch out — Sandbox test passed: it was installed in a new profile and registered with Harness. No obvious issues found.

The verdict — I would install it because it maps commands directly to buttons on the Feishu panel.

What it is — dsh-session-notification adds a Notifications section to the DeepSeek Harness settings panel. It sends browser alerts and plays sounds for four session states: completed, failed, question asked, and permission requested.

Who it is for — If you use DeepSeek Harness web GUI for multi-turn conversations and want notifications when sessions finish or prompt you without staying on the page, this plugin is suitable. People who do not use DeepSeek Harness web GUI or do not need session status alerts do not need to install it, because the feature relies on browser notification and sound capabilities.

Watch out — It passed sandbox testing in a clean profile. Shell command execution is flagged in static checks. Browser notifications are off by default and require user gesture permission. No other obvious issues found.

The verdict — I would not install it because it only adds browser-side features without core functionality changes, but if you run long sessions in the web GUI and need passive updates, it could be worth it.

What it is — dsh-im-connect integrates WeChat WeCom DingTalk Feishu Lark QQ Telegram with local DeepSeek Harness agent, with each IM chat as a separate workspace channel.

Who it is for — It is suitable to install this plugin when driving the DeepSeek Harness agent in WeChat WeCom DingTalk Feishu Lark QQ Telegram chats and completing tool approval in the original conversation. If you do not involve private chat access and whitelist settings, you do not need to install this plugin.

Watch out — No obvious pit was found. The sandbox test showed it registers successfully in a new profile. After installation, you need to restart dsh web and hard refresh the browser to see the setting page.

The verdict — I would install it because it allows completing tool approval in the original IM conversation, which provides mobile interaction not available in the web interface.

What it is — This is an MCP bridge plugin that lets ChatGPT Web create, view, continue and supervise DeepSeek Harness agent sessions while preserving DSH's native approval, sandbox and workspace security model.

Who it is for — If you want to use ChatGPT Web's natural language interface to create and manage DeepSeek Harness agent goals with external supervision while keeping DSH's native security controls, then this plugin fits.
If you only run DeepSeek Harness locally without any external chat interface integration, you do not need this plugin.

Watch out — Installation requires Node.js 22+ and a DSH runtime, added to a web profile via dsh plugin --profile web add; static analysis shows the plugin executes shell commands; sandbox testing passed when installed in a fresh profile and registered by Harness.

The verdict — I would not install it because it requires an extra MCP tunnel connection and executes shell commands, raising external interaction and security handling costs.

What it is — Task-event notification center supporting browser notifications and push channels for 6 event types.

Who it is for — For users handling subagent completion and turn-end task events requiring notifications, this plugin is suitable for installation. Users running alpha versions of DeepSeek Harness do not need to install it.

Watch out — No obvious issues found. Real testing passed with successful installation in fresh profile and registration into Harness.

The verdict — I would install it because it supports notification text redaction.

What it is — Provides email tools for DeepSeek Harness agent: list/read/search/send emails, attachment download, folder listing, with presets for QQ, Gmail, Outlook and multi-account support.

Who it is for — If your agent needs to handle emails from QQ or Gmail accounts, dsh-email is suitable. If your work focuses on code generation or data analysis, you don't need this plugin.

Watch out — Sandbox test passed in a new profile with successful registration. Requires providing an API key or token for the email accounts. No obvious runtime issues found.

The verdict — I would install it because it includes a send-approval gate for secure email sending in UI environments.

What it is — dsh-imessage provides a two-way iMessage channel for DeepSeek Harness over Photon, supporting sender allowlisting, session commands, in-chat approvals and questions, and a Settings page for device authorization and hosted-line setup.

Who it is for — If you need to interact with DeepSeek Harness via iMessage to handle in-chat approval requests and questions using a Spectrum model, install this plugin. Users who do not require iMessage as a transport method need not install it.

Watch out — Sandbox testing passed: successfully registered and loaded in a new profile. Compatible with DeepSeek Harness 0.1.0-rc.6 and Spectrum 12.7.x. No obvious issues found.

The verdict — I will install it because it provides iMessage as both input and output interface with verified compatibility. However, if iMessage is not needed, it is not worth the extra Photon project setup.

What it is — Integrate multiple messaging platforms into DeepSeek Harness for unified configuration and agent cross-platform chat.

Who it is for — When connecting WeChat, QQ, DingTalk, Lark, and Telegram to drive agent conversations in DeepSeek Harness, this plugin is suitable. If you only use a single messaging platform or do not need private-chat and group access controls, you do not need to install this plugin.

Watch out — Installation from source requires manually allowing the build script. It will execute shell commands. No obvious issues found.

The verdict — I would not install it because there is no sandbox test result yet.

What it is — Two-way bridge connecting DeepSeek Harness to WeChat (iLink) for turn-end and approval-request push, in-chat approve/reject and message injection, with persistent dedup and convergent long-reply chunking.

Who it is for — When running long tasks on a computer and needing remote monitoring, approval, and instruction injection via WeChat after leaving, this plugin is suitable. If you have already installed other WeChat bridge plugins like dsh-chatnode-wechat, dsh2wechat, or dsh-wechat-notify, you do not need to install this plugin.

Watch out — Sandbox test passed: installed in a new profile and registered by harness. It will execute shell commands. No obvious pitfalls found.

The verdict — This plugin is worth installing for its persistent dedup and convergent chunking in long tasks, but requires manually allowing its build script when installing from source.

What it is — dsh-acp-for-bitfun bridges BitFun to DeepSeek Harness via ACP v1 over stdio, integrating BitFun as a subagent for dsh sessions.

Who it is for — Users who need to delegate tasks to BitFun using the subagent_bitfun tool in DeepSeek Harness sessions are suitable for this plugin. Users who want to use BitFun outside of DSH do not need it.

Watch out — Requires BitFun CLI installed with bitfun acp doctor passing. The plugin executes shell commands to probe the command location on load and fails if not found. Sandbox testing succeeded in a fresh profile.

The verdict — I would install it because it enables using BitFun as a subagent in DeepSeek Harness sessions, provided BitFun CLI is installed.

What it is — The DSH notification center plugin triggers browser notifications and plays sound effects on events.

Who it is for — When using DeepSeek Harness to handle model requests that require approval, it is suitable to install this plugin to get immediate reminders. If the user mainly focuses on conversation completion without needing approval reminders, they can choose not to install this plugin.

Watch out — Sandbox testing passed: it can be installed and registered in a new profile. It will execute shell commands.

The verdict — I will install it because it can provide immediate reminders for model request approvals without cooldown limits, which helps with quick task confirmations.