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

5713HTMLMITSource

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.
  • Detected: terminal surface, requires credentials. Read the source before granting these.
  • A listing here is not a security review. 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

1.5k

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 packageJavaScript6d ago

AI review

dsh-im

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.

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

1.4k

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 packageJavaScript18d ago

AI review

dsh-pocket

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.

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

openpets

alvinunreal

1.2k

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 sourceTypeScript15d ago

AI review

openpets

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.

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 sourcePython10d 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
85

Desktop notifications for turn completions, with per-outcome controls and keyword rules.

Installed cleanly when we ran it

GitHub sourceJavaScript1mo ago

dsh-lark

omdsh-dev

55

Lark/Feishu bot channel for DeepSeek Harness: each chat drives its own agent, and tool approvals, model questions, and plan reviews return as cards answered by a button or a reply. Switch workspace and model from the chat (`/cd`, `/model`, `/new`), and run several bots that keep separate sessions and can hand turns to each other in one group.

Installed cleanly when we ran it

npm packageTypeScript1mo ago

AI review

dsh-lark

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.

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