dsh-discord-notify

One-way Discord webhook notifications for DeepSeek Harness (DSH).

The plugin can notify a Discord channel when:

• an agent turn starts;
• an agent turn ends;
• a selected tool is called; or
• a 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.

Security and privacy

• The webhook URL is registered as a DSH role('secret') setting. It is removed from remote settings reads and never returned to the browser after saving.
• Discord mentions are disabled with allowed_mentions.parse: [].
• Tool arguments are excluded by default because they may contain prompts, file paths, tokens, or other sensitive data.
• Regex-matched bash alerts include the matching command text by design.
• Delivery failures are logged without printing the webhook URL or request body.

Treat a Discord webhook URL like a password. Revoke it in Discord if it is exposed.

Installation

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

Configuration

The settings accordion exposes:

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.

Template variables

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.

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.

Composition configuration

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.

Event semantics

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.

Development

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.

Publishing

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.

License

MIT