DSH Marketplace

dsh-notification

omdsh-dev/dsh-notification

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

8911JavaScriptMITSource

Install

Add dsh-notification to DeepSeek Harness

Install into

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 yesterdayon DeepSeek Harness 0.2.2-rc.5.

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.

Security

What installing dsh-notification runs

Build scripts

No build script was blocked in our run.

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

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.

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

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