dsh-reach
把 DSH 的审批卡与提问卡推送到 IM 渠道(先支持微信),可在聊天里直接作答,带会话控制台、逐渠道安全与开放推送服务。
安装
dsh plugin --profile web add dsh-reach
沙箱测试结果
| 阶段 | 结果 |
|---|---|
| 1 安装 | ✓ |
| 2 列装 | ✓ |
| 3 挂载 | ✓ |
| 4 启动 | — |
四阶段在隔离沙箱里跑:安装(有网)→ 列装 → 挂载 → 启动(后三步断网)。
README
dsh-reach
dsh plugin --profile <name> add dsh-reach
English | [简体中文](README-zh.md) | [Español](README-es.md) | [Português](README-pt.md) | [हिन्दी](README-hi.md)
Multi-channel decision & remote-control bridge for DeepSeek Harness (DSH): pushes any workspace's approval/question cards to IM channels (WeChat iLink, Telegram, Feishu — plus QQ/DingTalk/WeCom v2 drop-in foundations) and answers them from chat, with a session console, per-channel security, and an open push service.











Status: Phase 1–3 complete (WeChat + Telegram + Feishu channels, v0.1.24); v2 channel foundations (QQ/DingTalk/WeCom) on the open reachChannels registry.
The design plan, competitor research, official contract verification, and
phased roadmap live in
[docs/design/03-rebuild-direction-and-plan.md](docs/design/03-rebuild-direction-and-plan.md).
Release (GitHub repo + npm publish) follows in a dedicated session.
📖 Ecosystem knowledge base — measured data, not marketing: plugin development guide · plugin-selection data · maintenance criteria.
<!-- star-cta -->
Install
dsh plugin --profile web add github:PerryLink/dsh-reach
# npm channel (published releases) dsh plugin --profile web add dsh-reach # git channel (latest main) dsh plugin --profile web add github:PerryLink/dsh-reach # alternates npx @deepseek-ai/dsh plugin --profile web add dsh-reach dsh1024 plugin --profile web add dsh-reach
Restart DSH after installation (bundle patches apply at startup).
⭐ 如果它帮到了你
这个插件是 DSH 插件家族的一员(95 个,全部 Apache-2.0)。如果你在用,给个 star —— 它不会解锁任何功能,但会让下一个人在搜索里更容易找到它。
English: part of a 95 plugin family for DeepSeek Harness. If it is useful, a star helps the next person find it — nothing is gated behind it.
What is dsh-reach?
Full evidence, including the host-version compatibility matrix: dsh-plugin-supersession-review-20261005.md.
Workflow overview: install → open panel → act. The examples below use the real command surface.
Maintenance status: 🧊 FROZEN
Frozen on 2026-10-05. No new features. This package still works, and it is not retired — but it no longer receives feature work. Only a genuine breakage will be fixed.
Maintainers treat this capability as one where the ecosystem has converged on a more widely adopted implementation, so effort has moved elsewhere. The comparison below was measured on 2026-10-05 and is recorded so nobody has to redo it.
· package · weekly downloads
this package · dsh-reach · 600
more widely adopted implementation · @xmanrui/dsh-im · 17,384
Why it is the mainstream choice. @xmanrui/dsh-im provides ten channels — WeChat, Feishu, WeCom, DingTalk, QQ, Telegram, WhatsApp, Slack, Discord and Matrix.
Compatibility. declares no dsh peers, so the compatibility guard never blocks it.
What this package still does that the alternatives do not. this package's differentiator was that the same bridge carried approvals and questions back into chat; the rival is broader in channel coverage
👉 For new work, @xmanrui/dsh-im is the mainstream choice. Existing installs keep working unchanged; nothing is being removed.
Full evidence, including the host-version compatibility matrix: dsh-plugin-supersession-review-20261005.md.
Compatibility
Surface · Status
Harness · DeepSeek Harness dsh-v0.2.1-alpha.1 (GitHub tag). Peer range >=0.1.2-rc.1 <0.2.0 \ · \ · >=0.1.5-alpha.1 <0.2.0 \ · \ · >=0.1.6-0 <0.2.0 \ · \ · >=0.1.7-0 <0.2.0; the dev/test pins deliberately stay on the published 0.1.7-rc.2 line, which is the face the typecheck:ci ruler measures (the plain typecheck ruler measures the checkout through tsconfig.json paths). Verified 2026-09-24 with the full gate chain; the bare-import + scratch-profile + keyless smoke run in the Compat workflow on every PR.
Node · ^22.19.0 \ · \ · >=24.0.0
Features (Phase 1)
- Cross-session decision push: approval/question cards from ANY workspace
are mirrored to WeChat (iLink/ClawBot) with stable #token ids and P{n}
numbering; reply 1/2, P1=1 P2=2, P1=Q1=2, or /rp /rq — answered
through the native pending waterfall (first reply wins with the GUI).
- Fail-closed security: first sender becomes the owner;
…(truncated)
以上内容来自 npm 上的 README,我们只做格式化,不改内容。
版本
npm 上共发布:24,最后更新 2026-10-31