MIT-licensed TypeScript DSH plugin suite for cross-instance messaging and event fan-out over persistent WebSocket, with shared-key auth and zero manual addressing for replies.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-09-05
License
MIT
01What can it help you accomplish?
Run message handoff and bidirectional event push across multiple DSH instances
Cross-instance / cross-machine message delivery, live-session enumeration and liveness pings over a persistent WebSocket host service
Operators and developers running more than one DSH instance that need reliable inter-instance messaging and event fan-out
Let the model address and message peer instances on its own
interconnect_send / _list / _ping / _reply tools; send auto-injects instanceId + sessionId, reply needs no manual addressing
Developers building multi-instance DSH workflows where the model should discover peers and reply without hard-coded addresses
02How to install into DeepSeek Harness
Not specified by the author
03DSH integration and capability boundaries
Native DSH plugins: a persistent-WebSocket interconnect host service plus model-visible send/list/ping/reply tools and a companion skill that register directly into ctx.interconnect and ctx.skills.
interconnect host service
peers mapping (instanceId → origin) and DSH_INTERCONNECT_TOKEN→persistent WebSocket delivery, live-session enumeration, liveness pings, and event fan-out via interconnect/event
registers the ctx.interconnect host serviceopens the /interconnect/link WebSocket endpoint with heartbeat and exponential-backoff reconnecttool-interconnect toolset
instanceId + sessionId + text (send/ping/list) or sessionId + text (reply)→model-visible interconnect_send / _list / _ping / _reply tools
send can wake an offline session via resumeskill-interconnect companion skill
model context (ctx.skills)→registers the dsh-interconnect skill documenting list / ping / send / reply usage
send auto-injects the sender instanceId + sessionIdonly registers when the transport layer is presentShared-key auth
DSH_INTERCONNECT_TOKEN bearer→fail-closed, timing-safe token comparison
rejects requests without a valid shared token
04Who is it for? When not to use it?
Good for
- Operators and developers running more than one DSH instance that need reliable inter-instance messaging and event fan-out
- Developers building multi-instance DSH workflows where the model should discover peers and reply without hard-coded addresses
Not for
- Requires a shared secret `DSH_INTERCONNECT_TOKEN` (bearer); the comparison is fail-closed and timing-safe, so every peer must share the same token to communicate.
- From 0.9 the transport is WebSocket-persistent only — there is no HTTP endpoint. Calls to an unconfigured or unreachable peer (send / ping / list) return `unreachable` with no HTTP fallback.
05Compatibility, maintenance and safety notes
- Requires a shared secret `DSH_INTERCONNECT_TOKEN` (bearer); the comparison is fail-closed and timing-safe, so every peer must share the same token to communicate.
- From 0.9 the transport is WebSocket-persistent only — there is no HTTP endpoint. Calls to an unconfigured or unreachable peer (send / ping / list) return `unreachable` with no HTTP fallback.
- `instanceId` is only a key in the peers map; the real dial origin comes from the mapped value. `instanceId` itself never appears on the wire and does not participate in routing.
MIT · maintained (no tagged release; README is the source of record)
06Frequently asked questions
What is dsh-interconnect?
A suite of three DSH plugins for cross-instance message handoff and bidirectional event push: an `interconnect` host service, a `tool-interconnect` toolset, and a `skill-interconnect` skill. It lets one DSH instance send messages to and receive events from other instances on the same or different machines.
How does the model talk to peer instances?
Through `interconnect_send`, `interconnect_list`, `interconnect_ping` and `interconnect_reply`. `interconnect_send` auto-injects the sender's `instanceId` and `sessionId`, and the receiver can reply with `interconnect_reply` using only its local session — no manual addressing required.
How does addressing work from 0.9?
Since 0.9 the transport is WebSocket-persistent only (no HTTP endpoint). You address peers by `instanceId` (a key in the `peers` map); the real dial origin comes from the mapped value. `instanceId` itself never appears on the wire and does not participate in routing.
What happens if a peer is down?
Calls to an unconfigured or unreachable peer (`send`/`ping`/`list`) return `unreachable` — there is no HTTP fallback, because from 0.9 the transport is WebSocket-only.
How is it secured?
With a shared secret `DSH_INTERCONNECT_TOKEN` (bearer). The comparison is fail-closed and timing-safe, so every peer must share the same token to communicate.
07Related DSH workflows
awesome-gpt-image-2
by freestylefly
Prompt-as-Code engine and template library for GPT-Image2, with 470+ reverse-engineered cases, 20+ production templates and distilled agent skills.
voyager
by voyager-crew
A browser-extension suite for Gemini, AI Studio, Claude, ChatGPT, and DeepSeek, with a prompt manager that works on any website, including DeepSeek Harness.
dsh-im
by xmanrui
把 IM 机器人接入 DSH：统一管理飞书/微信/钉钉/企业微信/QQ/Telegram/Discord/WhatsApp 八个渠道，扫码或凭据接入、流式回复与设置页管理
wegent
by wecode-ai
Plan, build, and deliver with an open-source, self-hostable AI workspace for coding, collaboration, and automation.
08Data and sources
跨实例消息互通与事件通知插件，用于 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (DSH)。
**`interconnect`** —— host 服务（`ctx.interconnect`）：
依赖 `interconnect` 服务，只有传输层存在时才注册进 `ctx.skills`。
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-09-05. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.