SeverusZh/dsh-notify-windows

## Core Features
- The plugin sends Windows desktop notifications from DeepSeek Harness when an agent session completes, fails, reaches an output limit, requests approval, or asks the user a question.
- It listens to turn/end events for session endings and uses the session title in the notification title while showing the ending reason and round in the body.
- It listens to approval/asked events and skips notifications automatically when the session approval policy is set to never.
- It detects tools.ask_user_question( calls inside run_code program source and extracts the question text for the notification body.
- It ignores subagent sessions by default and can optionally include them through configuration.

## Use Cases
- Users can leave the screen while an agent task runs and receive a notification when the main session finishes or stops with an error.
- Users can receive a prompt when an operation is waiting for approval instead of watching the DSH interface continuously.
- Users can be notified when an agent asks a question that requires an answer, including questions issued through run_code tool calls.

## Technical Details
- Notifications are sent through the Windows PowerShell 5.1 WinRT Toast API, and the plugin registers an AppUserModelId under HKCU without requiring administrator rights.
- Installation uses the dsh.bundle mechanism, where the npm package provides cordis.patch.yml to mount the dsh-notify entry after dsh plugin add.
- Configuration is applied by overriding the dsh-notify entry in the profile cordis.patch.yml, and the file is watched by the running DSH process.
- Clickable toasts can open the DSH Web GUI through a dshnotify:// protocol handler, focus an existing window when available, or fall back to the default browser.

## Notes
- The README identifies Windows 10 or Windows 11 as the platform, and notification delivery depends on Windows notification settings and Focus Assist behavior.
- Manual - insert: entries for dsh-notify cause a duplicate loader entry error.
- DSH 0.1.0-rc.8 front end does not consume the ?session=<id> parameter, so clicking a toast opens the DSH interface rather than directly locating the target session.