dsh-notify

If you run DeepSeek Harness headless tasks, the most annoying part is that the agent may finish, crash, get blocked, or pop up an approval dialog, and if you are not staring at the terminal you miss all of it. dsh-notify listens to key session-state events and pushes a message to the channel that matters to you: DingTalk, WeCom, QQ, ntfy, an A2A agent, an MCP tool, or even a local Windows voice announcement.

Four triggers map to real workflows. A turn/end event (completed, error, blocked, or max-tokens) fires a summary notification. An approval dialog or ask_user_question call alerts you immediately with a question digest. If no decision is made within ten minutes, the plugin escalates with high-priority channels plus a voice re-alert. A model-initiated notify tool, off by default, lets the agent push a message to you mid-run. Every notification flows through a unified queue with concurrency, exponential-backoff retries, and automatic primary-to-fallback failover; a short flush on dispose makes sure the last status still goes out before the process exits.

Privacy is the default posture: notifications carry only title, reason, duration, and timestamp. Body preview is off, and secrets are resolved via environment variables or the credentials service rather than stored in plain text. The plugin is pure Node with zero runtime dependencies and a build-free bundle that slots into dsh's patch shape. It is built for anyone who runs dsh background jobs and wants agent state piped into an IM bot, an automation pipeline, or a desktop voice cue, without touching the agent code.