Skip to content

dsh-notify

Verified

@lixiangzhong/dsh-notify Β· v0.1.4 Β· MIT Β· Web UI

Native system notification banners and a Dock badge when DSH waits for your answer, waits for approval, or finishes a turn.

Install

dsh plugin add @lixiangzhong/dsh-notify

Confirm the layer applied with dsh --profile default --dump-config β€” see the install guide.

Source

Tags

Readme

@lixiangzhong/dsh-notify

English | δΈ­ζ–‡

Native system notifications for DeepSeek Harness: a real notification-center banner and a Dock badge whenever the agent needs you.

What it notifies

Event When Banner body
Question The agent opens an ask_user_question card (including a plan review) Waiting for your answer
Approval The agent asks permission for a tool call Waiting for your approval
Turn end The agent finished a turn Turn finished

The banner title is the Session title, so several Sessions stay distinguishable.

Behaviour

  • Only while you are elsewhere. A focused, visible DSH window already shows the question card or approval bar, so nothing pops up then. Switching away, hiding the window, or closing it to the background keeps notifications working β€” the desktop shell keeps the Web client alive in the background.
  • One banner per request. A reconnect, re-render, or repeated Session-status update replaces the same banner instead of stacking a new one; at most three banners stay in Notification Center.
  • Click to answer. Clicking a banner brings the app forward and opens the Session that raised it.
  • Dock badge = Sessions waiting on you. Questions and approvals count; a finished turn does not. The Session you are currently looking at does not count either, so the badge clears itself as you work through them.
  • Follows your copy and system settings. Banner text follows the DSH interface language (English/Chinese); the alert sound follows the macOS notification settings for DeepSeek Harness.

Install

In the app: open Plugins in the sidebar, choose Add plugin, and enter @lixiangzhong/dsh-notify. The Install a third-party plugin menu item opens the same dialog for a package name, a Git repository, or a local directory.

From a shell with the dsh command on PATH:

dsh plugin --profile <profile> add @lixiangzhong/dsh-notify

dsh plugin forwards to pnpm inside the profile directory. The Electron-owned desktop profile is the exception: the npm CLI refuses plugin-management commands for it, so manage that profile from the app.

The bundle enables itself through cordis.patch.yml; there is no configuration.

Requirements

  • A DSH build whose Web GUI runs in a renderer with the W3C Notification and Badging APIs (the Electron desktop app qualifies).
  • macOS notification permission for DeepSeek Harness. If banners never appear, check System Settings β†’ Notifications β†’ DeepSeek Harness; a denied permission still leaves the Dock badge working.

Notes and limits

  • The plugin is client-only. While no Web client is running (the app is fully quit, or the renderer is reloading) there is nothing to notify from, and no one could answer a question in that state anyway.
  • Opening the same DSH Web GUI in an ordinary browser as well makes that page notify too; this version does not coordinate across pages.
  • Turn-end banners carry a fixed action-free body on purpose: they are a nudge, not a transcript.

Releasing

Publishing runs in CI; this repository stores no npm token.

  1. Bump the version and let npm write the release commit and tag: npm version 0.1.4 (add --no-git-tag-version if you prefer to write the commit and tag yourself).
  2. Push both: git push origin master and git push origin v0.1.4 (or git push --follow-tags). The v* tag starts the release workflow.
  3. .github/workflows/publish.yml checks that the tag matches package.json, runs npm test, and publishes through npm Trusted Publishing (OIDC), which also attaches a provenance attestation.

Prerequisite: the npm package must list .github/workflows/publish.yml as a trusted publisher (user lixiangzhong, repository dsh-notify) with Allow npm publish enabled β€” new configurations default to stage-only publishing. A trusted-publisher configuration expires unless its first successful publish happens within two days of creation.

License

MIT