dsh-notifier

Plugin overview

Unified notification & remote control for DSH: one notify() API, 25+ channels (Telegram / DingTalk / Feishu / WeCom / QQ bot / WxPusher / PushPlus / ServerChan / Bark / Discord / Slack / ntfy / webhook...), level routing (timeSensitive / active / passive) with tiered retry, multi-channel inbound approval (Telegram buttons, Feishu cards, QQ, WxPusher, WeChat iLink), official QR login for QQ/DingTalk/Feishu, a local web admin console, multi-agent routing, desktop notifications — and a mobile command center: !status / !stop / !retry agent control from your phone plus actionable notifications (view result / retry / logs buttons that call back into the agent). Secrets redacted, tool rate-limited, zero runtime deps — plus an open event source: other plugins can inject the notifier service (ctx.notifier) and subscribe to dsh-notifier/sent events, reusing notification without coupling.

Suitable scenarios

This guidance is based on the entry category, labels, and public information. Actual capabilities depend on installation and use in the GetRun Harness App.

• When the workspace needs to send task events to an appropriate notification channel, review this entry's description and labels such as plugin, notify, notification to judge whether it fits the task.
• Validate whether "dsh-notifier" fits the current task in a test session without sensitive data before using it in an active project.
• When comparing entries in the same category, review public stars, version, license, and labels together. Those fields are not promises of security, compatibility, or ongoing maintenance.