DeepSeek Harness (DSH) makes it difficult to learn in a timely manner whether a conversation or task has completed, encountered an error, or requires approval when you switch away from the window or the task is running in the background. The DSH Notification Center plugin solves this problem by using browser system notifications and audio cues.

Plugin Positioning

This is a third-party community plugin maintained by developer 610la and is not an official DeepSeek Harness product. It is open source under the MIT license and aims to provide DSH with a configurable notification mechanism to ensure that critical events are not missed.

Core Features

  • Notifications and audio cues: Supports browser system notifications and 21 built-in matching sound effects, with individually adjustable volume for each sound.
  • Desktop app adaptation: When DSH is packaged as a desktop application (Electron or Tauri), the plugin automatically switches to native system notifications from the host process (such as the Windows or macOS notification center) and does not rely on browser permissions.
  • Independent configuration: Each event (such as conversation completion, error, or awaiting approval) can be configured individually for notification switch, sound type (built-in/custom file/URL), and volume.
  • Scenario triggers: Sends reminders for events such as errors, length-limit truncation, being blocked, and awaiting approval. When the model requests permission or approval, it triggers an immediate reminder without being subject to the cooldown limit.
  • Persistence: Settings support automatic saving and are not lost after refreshing the page.

Installation and Enablement

Install it using the official CLI:

dsh plugin --profile web add @lyhalal/dsh-notification-center

Restart DSH after installation to make it take effect.

Configuration and Usage

  1. Quick entry: Find the 🔔 icon on the left side of the input bar to quickly toggle notifications/audio cues, authorize notification permissions, or test notifications.
  2. Master switches and event settings: Go to Settings -> Notification Center. Use the master switches to control browser notifications, audio cues, the notification permission test, and the cooldown interval. Use the event settings to configure specific scenarios such as conversation completion, subtask completion, and Workflow completion.
  3. Detailed configuration: Expand a specific event to set the sound type (one of the 21 built-in sounds or a custom sound), volume level, and switch state.

Notes

  • Browser environment: On first use, notification permissions must be authorized from the address bar.
  • Audio cue triggering: Due to browser autoplay policies, audio cues will only play after at least one user click within the page.
  • Desktop application: In the packaged environment, the “Notification Permission/Authorization” option in settings is automatically hidden because native notifications do not require browser authorization.
  • Manual stop: For manually stopped or interrupted generation tasks, notifications are disabled by default. They must be manually enabled in the “Stop Reason” setting.