Monitors session state in the DSH web app and sends desktop, browser, and third-party notifications for interactions, completions, and errors.
Install
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:ly6170/dsh-messager
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
A task notification plugin for DeepSeek Harness (DSH). Get system, browser, Feishu, WeCom, Discord, DingTalk, or Telegram notifications when a session needs approval or input, a task completes, or a task fails.
Compatibility
v0.3.5 supports DSH 0.2.0-rc.1 and compatible later 0.2.x releases. Keep the matching older plugin version for DSH 0.1.x. Upgrade DSH before installing this version; existing notification settings need no migration.
Install
DSH desktop app: Open Plugins in the top-left corner, choose Add plugin, enter dsh-messager, and install it. Restart DSH after installation.
CLI (npm package): Requires Node.js 20+, pnpm, and the DSH CLI. Install into the Web profile:
dsh plugin --profile web add dsh-messager
dsh web
When running DSH from its source repository, use pnpm dsh instead of dsh. Restart DSH if it was already running.
From source (optional for developers):
git clone https://github.com/ly6170/dsh-messager.git
cd dsh-messager
pnpm install
pnpm build
dsh plugin --profile web add .
dsh web
Use
Open Settings → Messenger (「通知&信使」), choose the events and channels you want, enter any webhook or bot credentials, and save. System and browser notifications are enabled by default; third-party channels are disabled by default. Browser notifications require site permission.
Notifications cover interactions, root-session task completion, and task errors. Running status does not trigger a notification. Saved settings take effect immediately.
Troubleshooting
- Settings section missing or config route returns 404: Check the active
webprofile, restart DSH, and verify DSH/plugin version compatibility. - No browser notification: Check site permission. By default, notifications appear only when the page is hidden or unfocused.
- Settings unavailable with
--patch: That development mode loads only the host side. Install withdsh plugin addto use the settings page.
Links
More in this category
xmanrui/dsh-im★ 1525
Connect IM bots to DeepSeek Harness via QR codes or bot credentials (9 channels: Feishu, WeChat, DingTalk, WeCom, QQ, Slack, Telegram, Discord, and WhatsApp).
shaobeichen/dsh-pocket★ 1396
Remote phone access to the DSH Web UI: scan a QR code for LAN or public (cloudflared tunnel) access with real-time sync, a mobile-adaptive layout, and a settings tab.
inclusionAI/Avernet#deepseek-harness-channel-bcn★ 572
Connects DeepSeek Harness to Avernet's Bot Collaboration Network over WebSocket V2, with automatic onboarding, isolated agent sessions, tool-call events, and multi-bot routing tools.
omdsh-dev/dsh-notification★ 85
Desktop notifications for turn completions, with per-outcome controls and keyword rules.
whyihaveyou/dsh-suite#plugin-notify★ 57
IM webhook and local notifications on turn completion, errors, or approval (Feishu/WeCom/DingTalk/Slack/Discord/custom).
omdsh-dev/dsh-lark★ 55
Lark/Feishu bot channel for DeepSeek Harness: each chat drives its own agent, and tool approvals, model questions, and plan reviews return as cards answered by a button or a reply. Switch workspace and model from the chat (`/cd`, `/model`, `/new`), and run several bots that keep separate sessions and can hand turns to each other in one group.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.