DSH Marketplace
中文

dsh-notification

omdsh-dev/dsh-notification

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

8510JavaScriptMITSource

Install

Add dsh-notification to DeepSeek Harness

via GitHub · GitHub source

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 5d 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-notification

  • Source of record: omdsh-dev/dsh-notification — 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.

What dsh-notification does

Layered log fragments pass through filters and converge into desktop notification shapes.

dsh-notification is a DeepSeek Harness plugin that shows desktop notifications when a session finishes a turn. DeepSeek Harness provides a bounded session projection containing the last turn’s reason, reply text and tool names; the browser client watches the session list’s live completion reminder, applies persisted preferences, and calls the browser Notification API. The host reads the existing session log without adding events, while preferences are stored in browser localStorage.

DeepSeek Harness loads the host and client parts through the web profile. Settings under Settings > Notifications control outcome toggles, literal or regular-expression keyword rules, manual dismissal, visibility filtering and a test notification. The host-side maxBodyChars setting in cordis.yml bounds the projected reply text; the default is 400.

This suits developers who keep the DeepSeek Harness web page open but work in another tab, session or workspace. It is not suitable for notifications after the page is closed, or for reconnect recovery: completions that occur while the page is disconnected are not re-notified. The plugin reaches the existing session log through a read-only projection and reaches the browser’s notification surface to display completion status; it adds no model-facing tool, prompt content or log event.

dsh-notification documentation

Configuring dsh-notification

DeepSeek Harness reads the host configuration for dsh-notification from cordis.yml:

Key Default Behaviour
maxBodyChars 400 Maximum size of the projected reply snippet; longer text is ellipsised by the host.

The web client stores preferences in browser localStorage. Under Settings > Notifications, Enable notifications is the master switch. Outcome controls default to notifications for completed and error, with aborted, blocked and token limit disabled. Keyword rules match the session title, the latest reply text and the latest tool names. Include rules require at least one match; an exclude match suppresses the notification. Rules can use literal or regular-expression matching and may be case-sensitive.

Commands and web profile

DeepSeek Harness installs the plugin with dsh plugin --profile web add. After installation, restart the web server so DeepSeek Harness loads both the host portion and the served client bundle. The default dsh web profile supplies the session list, settings shell and locale required by the client composition. The settings section can grant browser notification permission and send a test notification.

How dsh-notification behaves

DeepSeek Harness computes a session-list completion reminder for a live running-to-idle transition. The client deduplicates that reminder, checks notification permission and the current-session visibility gate, then creates a notification titled DSH finished. With Only notify when the task is out of view enabled, the current session is suppressed, while hidden pages and other sessions or workspaces can still notify. Notifications for one session replace one another. Require manual dismiss keeps a notification visible until dismissed.

The plugin does not change prompts or session logs, register tools, or add token usage. The model receives no new capability.

Known limits of dsh-notification

The page must remain open, and browser Notification permission must be granted. A denied site permission cannot be overridden inside the page. Notifications fire once per finished turn; disconnected completions are not replayed. Rules inspect only the title and latest turn, and clicking focuses the window without linking to the turn.

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

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 packageJavaScript5d 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 packageJavaScript17d 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 sourceTypeScript14d 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 sourcePython9d 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

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

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