MIT-licensed native dsh plugin for the DeepSeek Harness web GUI: desktop alerts for turn completions with per-outcome toggles and keyword rules. No harness change is needed — the host contributes a session projection and the client applies its own persisted preferences.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-08-28
License
MIT
01What can it help you accomplish?
Get a desktop alert when a DeepSeek Harness session finishes a turn while you're on another tab
A browser system notification via the `Notification` API (e.g. `new Notification("DSH finished", { body: "deploy done" })`), configurable per outcome and by keyword rules
Developers using the DeepSeek Harness web GUI who want to switch tabs and still know when DSH is done
Control exactly which turn completions notify
Per-outcome toggles (completed / error / aborted / blocked / token limit) plus include/exclude keyword rules
Users who want to be notified only for specific outcomes or sessions matching their keywords
02How to install into DeepSeek Harness
Prerequisites
- DeepSeek Harness web GUI with the default `dsh web` profile — the README notes it has the required client composition (session list, settings shell, locale)
- Browser permission for the `Notification` API — the client shows a notification only when the user has granted permission
Installation steps
- 01
Run `dsh plugin --profile web add https://github.com/omdsh-dev/dsh-notification/archive/refs/tags/v0.1.3.tar.gz`
$ dsh plugin --profile web add https://github.com/omdsh-dev/dsh-notification/archive/refs/tags/v0.1.3.tar.gz
- 02
Restart the web server so the host half and the served client bundle pick up the plugin
- 03
Configure preferences under **Settings > Notifications**
Verify the integration
Not specified by the author
03DSH integration and capability boundaries
Native dsh plugin for the DeepSeek Harness web GUI: host session projection + client `Notification` API, installed via the `dsh plugin` CLI — no harness modification and no model-facing tools
Per-outcome notification toggles
turn-end reasons from the host projection — completed / error / aborted / blocked / token limit→desktop notifications only for the enabled outcomes (default completed + error on, rest off)
Keyword include/exclude rules
session title, the turn's reply text, and its tool names; literal or regex matching with an optional case-sensitive flag→notifications only for sessions/turns that pass the include and exclude filters
Master switch
on/off toggle in Settings→turns off every notification while keeping the configured rules
off stops every notification while keeping rulesOut-of-view-only notify and per-session replace
session visibility (in view / hidden / another session open)→suppresses a notification only when its session is currently in view; notifications for the same session replace each other
Persisted client preferences
settings chosen under **Settings > Notifications**→preferences persisted in browser localStorage and applied by the client
Preferences persist in the browser (localStorage)Host-side body budget (maxBodyChars)
`maxBodyChars` config on the plugin row in `cordis.yml`→longer replies are ellipsized host-side; the reply body never exceeds `maxBodyChars`
04Who is it for? When not to use it?
Good for
- Developers using the DeepSeek Harness web GUI who want to switch tabs and still know when DSH is done
- Users who want to be notified only for specific outcomes or sessions matching their keywords
Not for
- Notifications require an open page and browser `Notification` permission: the browser shows them while the page is hidden but not after the tab is closed, and a denied site permission cannot be overridden from inside the page.
05Compatibility, maintenance and safety notes
- Notifications require an open page and browser `Notification` permission: the browser shows them while the page is hidden but not after the tab is closed, and a denied site permission cannot be overridden from inside the page.
- Notifications fire once per finished turn (a running→idle edge on any session); a completion that happened while the page was disconnected is not re-notified on reconnect.
- The rule subject is the session title plus the last turn's reply text and tool names — earlier turns are not matched.
- The notification body is a flat text snippet; the click action only focuses the window (no deep link to the turn).
MIT · last push 2026-08-19 · no tagged release
06Frequently asked questions
How do I install dsh-notification?
Run `dsh plugin --profile web add https://github.com/omdsh-dev/dsh-notification/archive/refs/tags/v0.1.3.tar.gz`, then restart the web server so the host half and the served client bundle pick up the plugin. Settings live under **Settings > Notifications**, where the section also grants browser permission and sends a test notification.
Do I need to change the DeepSeek Harness harness itself?
No. The README says 'No harness change is needed': the host contributes a session projection (a bounded summary of each session's last completed turn), and the client watches the session list's completion reminder and applies its own persisted preferences.
Which turn outcomes can trigger a notification?
There are per-outcome toggles for completed / error / aborted / blocked / token limit. Defaults are completed + error on, rest off; the host projection reports the turn-end reason.
How do the keyword rules work?
Include/exclude filters match against the session title, the turn's reply text, and its tool names. Include rules: at least one must match; exclude rules: a match suppresses. Rules support literal or regex matching with an optional case-sensitive flag.
What are the main limitations to know about?
Notifications require the page to be open and Notification permission granted — they show while the page is hidden but not after the tab is closed. They fire once per finished turn and are not re-notified on reconnect, and the body is a flat text snippet with no deep link to the turn.
07Related DSH workflows
dsh-open-in-vscode
by omdsh-dev
Open DeepSeek Harness workspace directories in VS Code directly from the web GUI.
fn-os-apps
by tnnevol
Tencent CodeBuddy model provider for DeepSeek Harness that signs in with browser OAuth instead of an API key, lists the CodeBuddy model catalog with the context, output, tool-calling, reasoning and image capabilities of each model, keeps multiple accounts with automatic failover to the next usable one, shows remaining quota in the composer with a token and credit usage panel, and completes automatable CodeBuddy growth tasks per account with an execution log. Install from npm with `dsh plugin --profile web add @tnnevol/dsh-codebuddy`.
dsh-lark-bot
by plutokeating
Feishu/Lark bridge for DeepSeek Harness: scan-to-connect PersonalAgent binding, streaming cards, git-worktree project workspaces, parallel per-scope tasks, multi-role agents, cross-session notify, in-chat model/key management, and a safety-net guardian that still answers in Feishu after dsh crashes.
dsh-session-notification
by dingyi222666
Notifications for four session states, with browser alerts and prompts.
08Data and sources
When a session finishes a turn, the browser shows a system notification (via the `Notification` API), so you can switch…
No harness change is needed: the host contributes a session projection (a bounded summary of each session's last complet…
dsh plugin --profile web add https://github.com/omdsh-dev/dsh-notification/archive/refs/tags/v0.1.3.tar.gz
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-08-28. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.