Skip to content
Back to search

dsh-notification

Desktop notifications for DeepSeek Harness turn completions, with per-outcome controls and include/exclude keyword rules.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/omdsh-dev--dsh-notification/badge.svg)](/listings/omdsh-dev--dsh-notification)

HTML

<a href="/listings/omdsh-dev--dsh-notification"><img src="/api/listings/omdsh-dev--dsh-notification/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

dsh plugin --profile web add https://github.com/omdsh-dev/dsh-notification/archive/refs/tags/v0.1.4.tar.gz

Restart the web server so the host half and the served client bundle pick up the plugin. The default `dsh web` profile has the required client composition (the session list, the settings shell, and locale).

Version `0.1.4` supports both the 0.1.1 and 0.1.2 Harness client package layouts and projection contracts.

The settings section lives under **Settings > Notifications**.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 84 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # dsh-notification
  2. Desktop notifications for the DeepSeek Harness web GUI. When a session finishes a turn, the browser shows a system notification (via the `Notification` API), so you can switch tabs and still know when DSH is done. Per-outcome toggles and include/exclude keyword rules control exactly which completions notify.
  3. 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.
  4. ```
  5. host: notification projection (last turn's reason/text/tools) --session/projection--> browser
  6. client: session list completion reminder (live, dedup) + persisted settings
  7. -> permission + current-session visibility gate
  8. -> new Notification("DSH finished", { body: "deploy done" })
  9. ```
  10. ## Install
  11. ```sh
  12. dsh plugin --profile web add https://github.com/omdsh-dev/dsh-notification/archive/refs/tags/v0.1.4.tar.gz
  13. ```
  14. Restart the web server so the host half and the served client bundle pick up the plugin. The default `dsh web` profile has the required client composition (the session list, the settings shell, and locale).
  15. Version `0.1.4` supports both the 0.1.1 and 0.1.2 Harness client package layouts and projection contracts.
  16. The settings section lives under **Settings > Notifications**.
  17. ## Settings
  18. | Setting | Default | Effect |
  19. | --- | --- | --- |
  20. | Enable notifications | on | Master switch; off stops every notification while keeping rules. |
  21. | Notify on completed / error / aborted / blocked / token limit | completed + error on, rest off | Which turn-end reasons notify (the host projection reports the reason). |
  22. | Keyword rules | none | Include/exclude filters matched 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. |
  23. | Require manual dismiss | off | The notification stays until dismissed. |
  24. | Only notify when the task is out of view | on | Suppress a notification only when its session is currently in view. A completion still notifies while the page is hidden or while another session/workspace is open. Turn it off to notify even for the session being watched. Notifications for the same session replace each other. |
  25. Preferences persist in the browser (localStorage). The section also grants browser permission and sends a test notification.
  26. ## Configuration
  27. Host-side tunables live on the plugin row in `cordis.yml`:
  28. ```yaml
  29. - id: dsh-notification
  30. name: dsh-notification
  31. config:
  32. maxBodyChars: 400 # projection body budget; longer replies are ellipsized host-side
  33. ```
  34. ## Model experience
  35. | Aspect | Effect |
  36. | --- | --- |
  37. | Token cost | None — notifications are UI-only and never enter a request. |
  38. | Tool calls | None — the model gets no new tool. |
  39. | Session log | Unchanged — the projection reads the existing log and adds no events. |
  40. | Prompt | Unchanged — no system-prompt section is registered. |
  41. ## Permission boundary
  42. - The host folds a pure projection over the session log (turn reason, bounded reply text, tool names) and the projection seam delivers it to the browser; the plugin writes nothing to the log and registers no model-facing tools.
  43. - The client watches the session list's completion reminder (a live "finished while not selected" edge the runtime already computes) and shows a notification only when the user has granted Notification permission.
  44. - Rule matching runs client-side against the projected content; the reply body never exceeds `maxBodyChars`.
  45. ## Development
  46. ```sh
  47. pnpm install # links the sibling dsh checkout for build and tests
  48. pnpm run check # typecheck + tests + build
  49. pnpm run test # vitest (host projection + composition, client decision/runner/helpers/section)
  50. pnpm run build # esbuild host/client/invariant bundles + tsc declarations
  51. ```
  52. The repo expects the harness checkout at `../dsh` for the dev-time `link:` resolutions. The composition spec boots the real `SessionStore` and `SessionProjectionRegistry` and proves the fold.
  53. ## Known limitations
  54. - Notifications require the page to be open (the browser shows them while it is hidden, but not after the tab is closed) and Notification permission granted; a denied site permission cannot be overridden from inside the page.
  55. - 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.
  56. - The rule subject is the session title plus the last turn's reply text and tool names — earlier turns are not matched.
  57. - Notification body is a flat text snippet; the click action only focuses the window (no deep link to the turn).
  58. ## License
  59. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.