dsh-discord-notify
用于 DeepSeek Harness 代理轮次、工具调用和匹配的 bash 命令的单向 Discord webhook 通知。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-discord-notify@0.1.1Discord Notify 以 dsh-discord-notify 发布，当前版本为 0.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →One-way Discord webhook notifications for DeepSeek Harness (DSH).
The plugin can notify a Discord channel when:
bash tool command matches a JavaScript regular expression.It only sends messages to Discord. It does not read Discord messages, expose commands, or allow Discord users to interact with DSH.
role('secret') setting. It is removed from remote settings reads and never returned to the browser after saving.allowed_mentions.parse: [].Treat a Discord webhook URL like a password. Revoke it in Discord if it is exposed.
dsh plugin --profile web add dsh-discord-notify
Restart the running DSH web profile, then open:
Settings → Plugins → Plugin configuration → Discord notifications
For local development:
dsh plugin --profile web add ./dsh-discord-notify
Installing a packed tarball is recommended for release testing:
npm pack
dsh plugin --profile web add ./dsh-discord-notify-0.1.1.tgz
The settings accordion exposes:
| Setting | Default | Behavior |
|---|---|---|
| Discord notification URL | empty | Write-only channel secret; no notifications are sent until configured |
| Notification display name | DeepSeek Harness | Sender name shown in Discord |
| Agent turn started | off | Sends a message for each durable turn/start event |
| Agent turn ended | on | Sends a message for each durable turn/end event and includes its reason |
| Selected tool calls | off | Sends when a tool/call event matches the selected-tool filter |
| Tools to notify | empty | Searchable checklist built from the tools exposed by every healthy agent preset; empty means every tool |
| Include tool arguments | off | Includes raw tool arguments in selected-tool alerts |
| Regex-matched bash commands | off | Enables command-specific matching for the bash tool |
| Bash command regular expression | empty | JavaScript regex syntax without / delimiters |
| Send test notification | — | Queues a test through the saved Host-only webhook; unsaved edits must be saved or discarded first |
| Advanced templates | built-in messages | Per-alert message templates with strict allowed and required variables |
Example bash patterns:
^(npm test|pnpm run build)$
(deploy|publish|terraform apply)
Invalid, oversized, or potentially catastrophic regular expressions and non-Discord webhook URLs are rejected before settings are saved. Regex matching is limited to the first 16 KiB of a bash command to protect the shared Host event loop.
Each alert type has its own allowed variable set. Templates use {{variableName}} placeholders. The Host rejects unknown variables, malformed placeholders, empty templates, and templates missing their required variables.
| Template | Available variables | Required variables |
|---|---|---|
| Agent turn started | sessionId, sessionName, workspaceName, turn | sessionId, turn |
| Agent turn ended | sessionId, sessionName, workspaceName, turn, reason | sessionId, turn, reason |
| Selected tool call | sessionId, sessionName, workspaceName, turn, step, toolName, arguments | sessionId, toolName |
| Matching bash command | sessionId, sessionName, workspaceName, turn, step, command | sessionId, command |
| Test notification | sentAt | sentAt |
Dynamic values are escaped before interpolation. sessionName comes from DSH's canonical logged session title and falls back to the session ID. workspaceName comes from canonical Workspace registry membership and falls back to the session working directory. arguments and command are already formatted as bounded Discord code blocks.
The package installs itself through cordis.patch.yml. A manual equivalent is:
- insert:
- id: discord-notify
name: dsh-discord-notify
config:
notifyTurnEnd: true
notifyTurnStart: false
notifyToolCalls: false
toolNames: []
notifyBashMatches: false
bashRegex: ''
includeToolArguments: false
username: DeepSeek Harness
Avoid putting webhookUrl in a committed composition. Configure it through the settings accordion or a private local configuration file.
The Host plugin observes DSH's canonical post-commit session/event feed. This provides exact durable turn/start, turn/end, and tool/call events across active sessions. Notifications are queued in event order and sent without blocking the agent loop.
The Host resolves every healthy agent preset's standing scope and reads ctx.tools.schemas(scope). The union of those exact callable names becomes the searchable tool checklist in settings and refreshes on DSH tools/change events. A selected tool that later disappears remains visible as Unavailable so it can be removed.
A bash match is evaluated against arguments.command from the bash tool's JSON arguments. Bash alerts are independent from the general tool-call filter, so a matching command can be enabled without enabling notifications for every bash invocation.
The test button increments a validated settings nonce. Its Host watcher renders the test template and sends it with the stored webhook secret; the Client never receives that URL.
Requires Node.js ^22.19.0 or >=24.0.0. The initial compatibility target is DSH 0.1.5-rc.2; the plugin uses that release's live settings scope and session/event contracts.
npm install
npm run check
npm run check validates syntax, runs tests, and inspects the npm package payload.
Maintainers should publish manually from a clean main branch after running the local release gate:
npm ci
npm run check
npm audit --omit=dev
npm publish --dry-run --json
npm whoami
npm publish
The final command publishes publicly because package.json sets publishConfig.access to public. A dry run does not authenticate or publish.
After publishing, install dsh-discord-notify from npm into a clean DSH web profile, restart DSH, and perform a focused settings and webhook smoke test.
MIT