
THEWOLFWALKER/dsh-notifier
141Last commit Aug 16, 2026
dsh-notifier DSH plugin
dsh-notifier provides a single notify() API that pushes session events and model-generated notifications to 25+ channels. It also enables remote approval and conversation from your phone, plus a web admin console and mobile command center with heartbeat, stall alerts, and stop buttons.
How to install the dsh-notifier DSH plugin
dsh plugin add dsh-notifierCopying does not run this command. Review the repository and version before installing the dsh-notifier DSH plugin.
dsh-notifier DSH plugin data source
dsh-notifier DSH plugin snapshot date: Aug 16, 2026
discovered
What the dsh-notifier DSH plugin can do
- Dual trigger lines: auto-push session events (turn/end, approval/asked, agent/error) and a model-facing notify tool.
- 25+ channels: Telegram, Slack, Discord, Feishu, DingTalk, WeCom, QQ, Teams, Bark, Pushover, ntfy, webhook, and more, with zero runtime dependencies.
- Level routing: timeSensitive / active / passive delivery semantics with tiered retries.
- Remote approval and conversation: answer approvals via Telegram buttons, Feishu cards, or reply 1/2; chat with your agent and steer mid-turn.
- Mobile command center (v0.5): long-task heartbeats, stall alerts, and a stop button on notifications.
- Web admin console: local-only dashboard, notification stream, channel bindings, session management, and credential forms.
- Multi-agent routing: bidirectional agent × channel matrix with auto-registration and CLI.
- Anti-disturb rules, daily digest, and secrets safe with environment variable references.
Where the dsh-notifier DSH plugin fits
- Get instant notifications when your DSH agent finishes a turn or encounters an error.
- Approve agent actions (e.g., executing commands) from your phone while away from the desk.
- Monitor long-running tasks with heartbeats and stop them if they stall, using the notification action button.
- Chat with your agent remotely via Telegram, Feishu, or QQ to inject follow-up instructions.
- Receive a daily digest of yesterday's notification traffic in a passive channel.
Who the dsh-notifier DSH plugin is for
- DSH users who want to stay informed about agent activity on their mobile devices.
- Developers building agent workflows that require human approval or remote interaction.
- Teams using DSH in multi-agent setups needing centralized notification routing.
dsh-notifier DSH plugin limitations
- Requires self-provided credentials (API tokens, webhook URLs, secrets) for each configured channel.
- Web admin console is accessible only from 127.0.0.1 (loopback) and requires a Bearer token.
- Some channels have rate limits, daily usage caps, or require a paid subscription (e.g., Pushover).
- Inbound channels for remote approval/conversation are limited to six: Telegram, Feishu, QQ bot, WxPusher, WeChat iLink, and DingTalk.
- Desktop notifications on Windows require the optional BurntToast PowerShell module.
- The plugin is in active development (v0.5+) and features may change.
dsh-notifier DSH plugin: from the repository README
Quoted from the THEWOLFWALKER/dsh-notifier README, the upstream source of the dsh-notifier DSH plugin. Copyright remains with the original authors.
> **Your agent, in your pocket.** — 通知、审批、遥控,全在你的手机里。 **English** · [**简体中文**](README.zh-CN.md)            , a notification card with a stop button appears on Telegram and Feishu. Tap the button to send a cancel command to the agent.
Is the web admin console accessible over the internet?
No, by default it listens only on 127.0.0.1 for security. You can change the bind address, but it's recommended to use a reverse proxy with authentication if exposing it externally.
What channels support remote conversation with the agent?
Six inbound channels: Telegram, Feishu, QQ bot, WxPusher, WeChat iLink, and DingTalk. You can send plain text to follow up or inject, use '!' prefix to steer mid-turn, and a merge window reassembles rapid typing.