DSH Marketplace

plugin-notify

whyihaveyou/dsh-suite#plugin-notify

IM webhook and local notifications on turn completion, errors, or approval (Feishu/WeCom/DingTalk/Slack/Discord/custom).

6315HTMLMITSource

Install

Add plugin-notify to DeepSeek Harness

This plugin lives in a subdirectory of a larger repository, and `dsh plugin add` cannot reach it — it forwards to pnpm, which reads everything after `#` as a git branch or commit. Clone the repository and add the plugin through DSH's plugin panel using a repository source, or ask the author to publish it to npm.

Due diligence

Before you install plugin-notify

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

Security

What installing plugin-notify runs

Build scripts

Not measured — we have not installed it yet.

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

shell commands (bash, exec, spawn …); API keys, tokens or passwords

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 — 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.

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 plugin-notify does

Abstract diagram of event signals branching to webhook receivers and a local notification node.

plugin-notify is a DeepSeek Harness plugin that sends notifications when a turn completes, an error occurs, or an approval is pending. It can deliver these notifications through IM webhooks for Feishu, WeCom, DingTalk, Slack, Discord, or a custom destination, and can also produce local system notifications.

The available description identifies the notification events and delivery types, but does not document the implementation details: no hook name, command, configuration key, file path, payload format, or default is provided in the available README. DeepSeek Harness users should therefore treat the repository source as the reference for wiring and deployment rather than assuming a particular configuration interface.

plugin-notify is intended for users who need turn-state alerts outside the DeepSeek Harness interface, especially when approval or failure events must reach an external messaging service. It is the wrong choice when local notifications or existing DeepSeek Harness UI feedback are sufficient, or when the required messaging service cannot accept webhooks. The catalogue flags a terminal surface and a credential requirement. Those flags indicate that installation should be reviewed for terminal access and that configured notification destinations may require credentials; the README excerpt does not specify the exact terminal operations or credential names. No one-line installation command is listed for this plugin.

plugin-notify documentation

What plugin-notify documents

The available README describes plugin-notify as a notification plugin for three event conditions: turn completion, errors, and pending approval. It does not provide a command reference, configuration schema, payload specification, or destination setup procedure.

Delivery targets for plugin-notify

The documented delivery options are:

Destination Mechanism
Feishu IM webhook
WeCom IM webhook
DingTalk IM webhook
Slack IM webhook
Discord IM webhook
Custom destination IM webhook
Local system Local notification

The README does not define separate commands or configuration keys for these destinations. It also does not state whether all destinations use the same payload, how a custom webhook is shaped, or how local notifications are enabled.

Requirements and limits

The catalogue marks plugin-notify as requiring credentials and as having a terminal surface. The available README does not name the credentials, describe their storage, or explain which terminal operations the plugin performs. These details should be checked in the repository before granting the plugin access to an agent profile.

DeepSeek Harness users should also note that no one-line installation command is listed for plugin-notify. The available source establishes the notification scope and delivery categories only; it does not establish a minimum DeepSeek Harness version, supported operating systems, default settings, retry behaviour, or failure handling.

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 plugin-notify

dsh-im

xmanrui

2.4k

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

Installed cleanly when we ran it

npm packageJavaScript28d ago

AI review

dsh-im

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.Read the source
Details

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