Skip to main content

How to use dsh-im-bridge

Two-way WeChat (iLink) bridge: turn-end and approval-request push, in-chat approve/reject and message injection, persistent dedup and convergent long-reply chunking; channel layer extensible to other IMs.

This article is auto-derived from indexed fields (wiki / faq / compatibility_json), not freshly AI-generated.

This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.

Quick start

Two-way WeChat (iLink) bridge: turn-end and approval-request push, in-chat approve/reject and message injection, persistent dedup and convergent long-reply chunking; channel layer extensible to other IMs.

— source: plugins.ai_summary

Install & verify

dsh plugin --profile web add github:BiBoyang/dsh-im-bridge

Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.

— source: plugins.install

Key points

  • DSH → 微信：turn 完成 / 出错 / 被阻塞、批准请求（含工具名与原因）实时推送
  • 微信 → DSH：回复文本注入绑定会话；回复「批准 / 拒绝」应答 pending approval；/bind <session> 切换绑定会话
  • iLink 扫码登录，单用户白名单，消息去重、长回复分段、.. / !! / 超时合并
  • 消息去重是持久的：iLink 的轮询 cursor 不落盘，重启后全靠去重防重复回复。本插件用持久化去重表（跨重启有效）+ 内存 FIFO 双层判重，而不是只在内存里记 msg_id。
  • 长回复分段是收敛的：微信单条消息有长度限制，按 1200 字符（Unicode 码点）拆分，分段前缀 （i/n） 的长度参与递归收敛，不会出"第 3/2 段"；某段发送失败即停后续段并持久化补发队列，避免乱序。

— source: plugin_wiki.readme_en (fallback readme_raw)

Pitfalls

Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.

— source: general rule

How to use dsh-im-bridge