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.

5412JavaScriptMITSource

Install

Add dsh-notifier to DeepSeek Harness

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 15d ago.

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

  • Source of record: THEWOLFWALKER/dsh-notifier — present in the community registry that DSH's own plugin market installs from.
  • Licensed under MIT.
  • Detected: terminal surface. 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 — 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

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

deepseek-harness-channel-bcn

inclusionAI

571

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 sourcePython11d 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-notification

omdsh-dev

85

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

Installed cleanly when we ran it

GitHub sourceJavaScript1mo ago
1Details

plugin-notify

whyihaveyou

57

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

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

GitHub sourceHTML5d ago

AI review

plugin-notify

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