dsh-interconnect: Cross-Instance Message and Event Interconnect Plugin for DeepSeek Harness
chinesezjc/dsh-interconnect
DSH plugin for cross-instance message/event handoff with HTTP/WS bidirectional push.
Enable multiple DeepSeek Harness instances to send messages, probe liveness, and push events bidirectionally for cross-machine collaboration.
dsh plugin --profile web add github:chinesezjc/dsh-interconnect- Category
- Integrations & Connections
- Platform
- DSH-Plugin
- Author
- chinesezjc
- Distribution
- Plugin
dsh-interconnect Key Features
dsh-interconnect Repository
dsh-interconnect Repo Summary
dsh-interconnect is a DeepSeek Harness (DSH) plugin for cross-instance message/event handoff, maintained by Chinesezjc under the MIT license, last updated in 2026-08. It solves the problem of sending messages, probing liveness, and pushing events bidirectionally between DSH instances (same instance, different machines, or other DSH instances on different machines). Core capabilities include a host-level service interconnect (with HTTP and WebSocket endpoints) and a model-visible tool tool-interconnect (providing interconnect_send and interconnect_ping).
What core capabilities does the dsh-interconnect DSH plugin provide?
The interconnect service exposes /interconnect/* endpoints supporting send (message delivery) and ping (liveness probe), and a /interconnect/link WebSocket endpoint for bidirectional real-time event streaming with heartbeat and exponential backoff reconnection. Events support both HTTP and WebSocket fan-out, with inbound events emitted as interconnect/event. Authentication uses a shared secret (DSH_INTERCONNECT_TOKEN, bearer, fail-closed, timing-safe comparison). tool-interconnect lets models send messages to a specified session on a peer instance via interconnect_send and probe peer liveness/identity via interconnect_ping.
How to install dsh-interconnect?
The package is published on npm (dsh-interconnect) and also supports installation from a local path. Installation command:
dsh plugin --profile web add github:chinesezjc/dsh-interconnect
Or from npm:
dsh plugin --profile <name> add dsh-interconnect
After installation, restart the web service for the host side to take effect, and set the same DSH_INTERCONNECT_TOKEN in both instances' .credentials.yaml as the shared secret.
What are the architecture and development dependencies of dsh-interconnect?
Both plugins are attached to the host composition: interconnect is a process-level service across sessions and machines, requiring host level; tool-interconnect is also placed on host because interconnect does not have TypeRT @Remote/Gateway bindings, and placing it in an isolate realm would prevent tool lines from injecting into that service. Development relies on the public DeepSeek Harness monorepo as a sibling checkout, with ws as a runtime dependency provided by the host's node_modules.
How is dsh-interconnect verified?
The project passes 22/22 unit tests (17 service + 5 tool), with clean type checking and build. Bidirectional interoperability has been tested between two machines, including message delivery, WebSocket event streaming, and agent reverse-sending via interconnect_send. CI (GitHub Actions) clones the public DSH repository as a sibling and runs pnpm run check. The source of delivered messages is { kind: 'plugin', plugin: 'dsh-interconnect' }, allowing the receiving agent to distinguish cross-instance delivery from local user input.