AI Agent Hub
Back to plugins
🧰

dsh-maestro-notifier

Web Tools Updated 2026.09.15

Run the following command in DeepSeek Harness:

dsh plugin install ddtcorex/dsh-maestro-notifier

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install ddtcorex/dsh-maestro-notifier in DeepSeek Harness to install this plugin; the source repository is https://github.com/ddtcorex/dsh-maestro-notifier

About this plugin

Plugins in the DeepSeek Harness ecosystem often need to push a short message to the user — a job finished, a config migration failed, a scheduled task fired — yet doing the HTTP call, timeout, and error fallback by hand every time is repetitive and error-prone. dsh-maestro-notifier turns that into a one-line send() call backed by a tiny in-memory provider registry.

The defining design choice is never-throw. An unknown provider, a missing target, or a 10-second network timeout all resolve to a structured { sent: false, reason } result instead of an exception, so callers write notify calls the way they write log lines — no try/catch in sight. The built-in Telegram transport uses protect_content, disables link previews, enforces a 10 s timeout, and guarantees credentials never appear in logs. Message wording is entirely the consumer's job; this package is a pure transport and never authors domain text.

If you are building a dsh-maestro-* plugin or any Harness runtime feature that needs to push a brief notification, this removes the provider plumbing, default-target resolution from ~/.dsh/maestro/settings.json, and degradation logic from your checklist. Just register, send, and move on.

Use Cases

  • Push a one-way Telegram message after a task completes
  • Send an alert notification when a migration or scheduled job fails
  • Share a single provider registry so multiple plugins route through one exit

Best For

  • Engineers building plugins in the dsh-maestro-* suite
  • Developers who need to push a brief message to end users at Harness runtime
  • Teams that want to skip try/catch, timeout retry, and credential handling in their notification code