DSH Marketplace

dsh-notifier

THEWOLFWALKER/dsh-notifier

DSH notification & remote-control plane: one `notify()` API across 28 outbound channels, six inbound control channels, phone approvals/questions/task control, a Native DSH Notify & Control UI, live outbound hot-apply, multi-agent routing, and zero runtime dependencies.

5613JavaScriptMITSource

Install

Add dsh-notifier 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

DeepSeek Harness 0.2.2-rc.5 refuses the latest release

From 0.2 DeepSeek Harness checks a plugin's dsh range before installing anything, and refuses the whole command when the running version is outside it. The latest release asks for 0.1.7-alpha.1 || 0.1.7-alpha.2 || 0.1.7-rc.1 || 0.1.7-rc.2; we ran 0.2.2-rc.5.

dsh-notifier@0.10.2 is the newest release DeepSeek Harness 0.2.2-rc.5 accepts, and it installed when we ran it:

dshmarketplace-cli reads your dsh version and installs the release it accepts:

Why DeepSeek Harness refuses plugins, and every way around 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 todayon DeepSeek Harness 0.2.2-rc.5.

Due diligence

Before you install dsh-notifier

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

Security

What installing dsh-notifier runs

Build scripts

Not measured — DSH refused the latest release before running anything.

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

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

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

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-notifier does

Abstract event streams pass through layered routing filters into many notification channels, with control signals returning upstream.

dsh-notifier is a DeepSeek Harness plugin that routes agent and session notifications to messaging, push, desktop and webhook channels through one notify() API. DeepSeek Harness can send turn/end, approval/asked and agent/error events automatically, while the model can call the notify tool with a message, channel and title. Each message passes through timeSensitive, active or passive routing, multi-agent bindings, channel adapters and tiered retries. The configuration is added to cordis.patch.yml; other plugins can use the injected notifier service and subscribe to dsh-notifier/sent.

dsh-notifier also accepts inbound actions through supported channels. Telegram buttons, Feishu cards, QQ, WxPusher and WeChat iLink can handle approvals; mobile messages can send follow-ups, inject content, steer a turn, mute a session, or control an agent with !status, !stop and !retry. Long-running sessions can produce heartbeats and stall alerts, with stop actions on Telegram and Feishu cards. A local, loopback-only web console manages channels, bindings, sessions and members.

This is intended for operators who need remote approval, status delivery or agent control across several notification services. It is a poor fit when outbound network messaging or inbound remote control is not wanted, or when existing session notifications are sufficient. The terminal-surface risk comes from remote actions that can steer or stop an agent; those actions operate through the agent’s existing permissions. The README targets Node.js 22+ and states that runtime dependencies are not required.

dsh-notifier documentation

Configuring dsh-notifier

DeepSeek Harness loads dsh-notifier into a named profile. Add an entry to cordis.patch.yml with a config.channels list. Each channel has a type and channel-specific credentials, such as botToken and chatId for telegram, webhook and secret for dingtalk, or key for bark. The README lists 27 channel types, including Telegram, Slack, Discord, Feishu, DingTalk, WeCom, QQ bot, Bark, ntfy, Gotify, WxPusher, PushPlus, Server酱, webhook, bell and desktop.

Set admin.enabled: true to enable the local web console. The console is loopback-only and provides dashboard, notification, member, binding, session and channel pages. Channel credentials are masked in the console, which also supports test sends and QR scanning for supported login flows.

How dsh-notifier behaves

DeepSeek Harness automatically forwards turn/end, approval/asked and agent/error events. The model can call the notify tool with message, channel and title. Delivery resolves the level (timeSensitive, active or passive), multi-agent routing and channel adapter before applying tiered retries, debouncing, deduplication and rate limits. Long tasks use a default 15-minute heartbeat start; a default 10-minute period without events raises a stall alert.

Commands and integrations

Inbound messages can answer approvals, send plain-text followup or inject content, and use a ! prefix to steer a turn. !status, !stop and !retry provide mobile agent control. /quiet and /unquiet mute or restore a session’s pushes. Other plugins can inject the notifier service with ctx.inject(['notifier'], …) and subscribe to ctx.on('dsh-notifier/sent'). Source calls are limited to 10 per minute and clamped to 20,000 code points.

Requirements for dsh-notifier

The README targets Node.js 22+. Profile-targeted plugin installation requires DeepSeek Harness 0.1.0-rc.6+. The README states that dsh-notifier has zero runtime dependencies.

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-notifier

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