Plugin directory / Automation / dsh-push
dsh-push
Verified · install-tested on dsh kiim-wong
What it does
Push DeepSeek Harness agent lifecycle notifications to configurable channels
Works — verified, early-stage project
Push DeepSeek Harness agent lifecycle notifications to configurable channels It installs cleanly and boots without issues in our testing. It's early-stage but functional.
“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.
README
dsh-push
English | 简体中文
Push DeepSeek Harness agent lifecycle notifications to Bark, Feishu, WeCom, DingTalk, ntfy, or a generic webhook.
Installation
Install from npm:
dsh plugin --profile web add dsh-push
dsh plugin --profile headless add dsh-push
To install from GitHub, pin the repository to a commit:
dsh plugin --profile web add github:kiim-wong/dsh-push#<sha>
Git installations run the package's prepare script. Before the first installation, allow the package to build in the target profile's pnpm-workspace.yaml:
allowBuilds:
dsh-push: true
The package mounts itself as dsh-push through cordis.patch.yml. It does not require changes to the dsh monorepo or write to the profile's patch configuration.
Configuration
The default configuration path is $DSH_HOME/dsh-push/config.json. Set DSH_PUSH_CONFIG to use another path. Start with config.example.json. Environment variable references support $VAR and ${VAR}. Logs are written to push.log in the configuration file's directory.
Each channel requires at least its type and destination. Keep secrets in the configuration file or environment variables, not in cordis.patch.yml.
Supported events are idle, interrupted, needInput, and exit. minDurationSec filters idle notifications but does not affect interrupted notifications. Subagents are excluded by default; set includeSubagents: true to include agents whose session header has origin: "subagent".
/push command
When the command service is mounted, dsh-push provides /push status, list, get, set, enable, disable, test, events, on, and off. Headless compositions without the command service still load the notification event listeners.
Limitations
Notification delivery is not retried. Each request has an independent timeout, and process teardown uses a bounded flush. dsh has no equivalent of pi's session quit event, so exit means the plugin tree is being disposed, not that an individual web session closed. Notification bodies contain lifecycle summaries, not conversation content.
Channel implementations retain the protocols and signing algorithms from pi-agent-push. This package adapts only the event and command layers to Cordis.
Install
Install the catalog once, then DeepSeek Harness can find and install any plugin from this site automatically:
dsh plugin add dshbase-catalog Then say "install dsh-push for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.
Web profile:
dsh plugin --profile web add dsh-push Headless (CLI) profile:
dsh plugin --profile headless add dsh-push Package
npm: dsh-push · version — · tested on dsh 0.1.0-rc.6
Test report
Verified end-to-end: L1 install + L2 load + L3 runtime Q&A on dsh 0.1.0-rc.6.
When to use it
Automate a repetitive job — scheduling, chaining tasks, or reacting to events — so it runs without you starting it.
Who it's for
Users with recurring work who want it cron-style and hands-off rather than manually triggered.
For developers — extending it
Triggers and task templates are the seams — add event-driven or file-watch triggers, and richer workflow composition.