ben7am1n/dsh-webhook-bridge
dsh-webhook-bridge is a generic webhook receiver for DeepSeek Harness: POST to a local endpoint and wake a dsh agent. CI, monitoring, or any HTTP-capable service can feed messages to a harness agent over plain HTTP. It exposes a small local HTTP server where each request to POST /hook/:channel delivers a message to that channel's agent session, and committed assistant text can stream back to an optional callback URL. It is a protocol driver in the dsh extension model — the same role as the official ACP/JSON-RPC bridges, but for any system that can send HTTP.
Install
dsh plugin --profile web add github:ben7am1n/dsh-webhook-bridgeREADME (2026-08-31): local checkout cd /path/to/deepseek-harness && pnpm dsh plugin --profile web add /path/to/dsh-webhook-bridge, or from GitHub pnpm dsh plugin --profile web add github:<you>/dsh-webhook-bridge (pnpm ≥10 may block the build script — add the printed package key to <profile>/pnpm-workspace.yaml under allowBuilds). npm name not published (404 verified). Uninstall: pnpm dsh plugin --profile web remove dsh-webhook-bridge.
Compatibility
DSH web profile; node:http only; zero runtime deps beyond the official schema library; MIT.
Details
- Repo: ben7am1n/dsh-webhook-bridge
- Category: Other
- Stars: 1
- Version: repo ben7am1n/dsh-webhook-bridge
- Last push: 2026-08-13
- First seen: 2026-08-13
Recent updates
Generic webhook receiver; POST /hook/:channel → agent session; optional callback URL streaming; node:http only; protocol-driver role.
FAQ
- What can trigger an agent?
- Any HTTP-capable service — CI, monitoring, or custom tooling — by POSTing to /hook/:channel on the local server.
- Can the agent reply to the caller?
- Yes — committed assistant text can stream back to an optional callback URL you configure.
- What are the dependencies?
- None beyond the official schema library — it uses node:http only.
Alternatives
Sev7een/dsh-plugin-automations · omdsh-dev/dsh-web-ui-notify · ben7am1n/dsh-telegram