dsh-wechat-bot

English · 简体中文

Put DSH in your pocket — switch workspaces, sessions, and models straight from WeChat.

A scan-to-login WeChat bot powered by the official WeChat iLink Bot API (ilinkai.weixin.qq.com) — pure HTTP, zero external dependencies. WeChat messages flow straight into your DSH sessions and the agent replies with the full conversation history. The kicker: send one exact command in WeChat to switch to the very conversation you're having in the GUI — or hop to another workspace entirely — without ever touching your computer.

✨ The killer feature: WeChat is your remote control

Once you've bound a session, your phone isn't just another chat window — it's a remote control for DSH. Switch workspaces, switch sessions, switch models — all from WeChat, all without a computer.

Switch workspaces / sessions in WeChat

You: 切换会话
Bot: 📂 Please pick the session to switch to (reply with a number or title):
     1. 📁 proj (D:\proj) → session "微信助手"
     2. 📁 proj (D:\proj) → session "dsh更新状态查询"
     3. 📁 工作区A (C:\work) → session "周报"
You: 3
Bot: 📂 Selected: 工作区A (C:\work) → session "周报"
     Summarize this session before switching? Reply "是" or "否" (anything else cancels).
You: 是
Bot: ✅ Switched: 工作区A (C:\work) → session "周报"
     📝 Session summary:
     · Topic: weekly report
     · Done: data aggregation table
     · To-do: send to manager
     Future WeChat messages will go to this session.

• "切换会话" (switch session): lists sessions across all workspaces → reply with a number or title to switch instantly
• "切换工作区" (switch workspace): lists workspaces first, then that workspace's sessions → pick and switch
• "当前工作区" / "当前会话" (current workspace/session): check which workspace and session you're bound to right now (including the session id)
• The binding persists, so future messages keep flowing into the new session — conversation memory carries over seamlessly
• Jump to a session in another workspace in one step; projects stay isolated yet are one command apart

Read the room before you switch — with AI

Once you pick a target session, the bot asks "summarize first?" — reply "是" and it AI-summarizes the session (topic / progress / to-dos) so you can see what that conversation is about before you switch. Perfect for handovers, checking progress, or hopping into a different task.

More than switching: change models, create workspaces/sessions

You: 切换模型
Bot: Current model: deepseek-official / deepseek-v4-flash (effort high)
     Available models (reply with number or name):
     1. opencode-go / deepseek-v4-pro
     2. opencode-go / minimax-m3
     3. deepseek-official / deepseek-v4-flash
You: 2
Bot: Selected opencode-go / minimax-m3 — now pick the reasoning effort (off/high/max):
You: max
Bot: ✅ Model switched: opencode-go / minimax-m3 (max)
     Future WeChat messages in this session will use this model.

Only the exact words trigger interception (trailing punctuation like "切换会话。" is tolerated). There are nine: "切换会话", "切换工作区", "新增工作区", "新增会话", "切换模型", "当前工作区", "当前会话", "当前模型" and "统计用量". Every other message — including phrasings like "切到 xx" or "换到 xx" — goes straight into the currently bound session as a normal chat: no interception, no extra model calls. "切换模型" overrides only this WeChat session (per-chat); otherwise the DSH global default model is used. Permission mode is controlled by DSH global config (sandbox-policy), not by this plugin.

Other highlights

• ✅ Official iLink Bot API — no unofficial protocols, low ban risk
• ✅ QR-code login — scan to create/bind a Bot assistant, no personal WeChat takeover
• ✅ Free — no paid tokens or gateways
• ✅ Zero dependencies — pure HTTP, only qrcode for rendering the QR image
• ✅ Continue existing conversations — WeChat and an existing DSH session share one conversation history, nothing gets lost
• ✅ Two-way sync — messages and replies are written into the session in real time (visible in the GUI); you can keep chatting from either side
• ✅ Persistent memory — sessions survive restarts and resume automatically
• ✅ Built-in GUI settings — a dedicated section in DSH Settings for login, status, binding, and the workspace root — applies immediately

Installation

Option 1: From GitHub (recommended)

dsh plugin --profile web add "github:Snowfly11531/dsh-wechat-bot"

This plugin is zero-build: the source IS the artifact (the lib/ folder loads directly). There is no prepare script, so pnpm's build-script allowlist (allowBuilds) is not needed — it works right after install.

Option 2: From npm (once published)

dsh plugin --profile web add dsh-wechat-bot

Option 3: Local development (source in this repo)

git clone https://github.com/Snowfly11531/dsh-wechat-bot.git
dsh plugin --profile web add link:/absolute/path/to/dsh-wechat-bot

Restart dsh web after installation.

Quick start

1. Restart dsh web to load the plugin
2. Open Settings → WeChat Bot (a dedicated sidebar section)
3. Click Get QR code and scan it with WeChat to log in
4. Bind a session (required) — see below
5. Message your bot in WeChat — replies come from your DSH agent

Once bound, try "切换会话" in WeChat — that's what makes this plugin unique.

UI preview

Screenshots are no longer shipped with the source to avoid leaking personal WeChat chat_id values.

Unbound chats are ignored: the bot replies with a hint to bind a session first.

The killer use case: plug WeChat into the conversation you're already having

① You're mid-conversation with an agent in the DSH GUI (e.g. discussing a plan)
        │
② Open Settings → WeChat Bot → Mode 1 "Choose existing session"
        │       pick that session → Bind
        ▼
③ On the go, send a message to the bot in WeChat
        │
④ The agent replies with the FULL context — same person, same conversation

• WeChat messages enter that session; the agent's reply is written into the session (visible in the GUI) and sent back to WeChat
• Back at your desk, open that session in the DSH GUI and keep chatting; the next WeChat message is answered with the updated context — both sides always share the same memory
• Restart dsh and the session resumes automatically; WeChat continues right where it left off

Tip: start the conversation in the GUI first, then bind it to WeChat — the smoothest experience.

Binding a session

Open Settings → WeChat Bot and use the Binding section. Two modes:

Mode 1: Choose an existing session (recommended — continue a conversation)

[●] Choose existing session    [○] New session
chat_id:   (auto-detected, editable)
Workspace: [dropdown ▾]
Session:   [dropdown ▾]   ← shows session titles
[Bind]

• This is continuation, not a new chat: WeChat messages flow into the chosen session and the agent replies using its entire history (including everything said in the GUI)
• Bound by workspace + session title, resolved dynamically at runtime — survives restarts even if session IDs change, as long as a session with the same title exists in that workspace
• WeChat and GUI stay in sync (see the use case above)

Mode 2: New session

[○] Choose existing session    [●] New session
chat_id:         (auto-detected, editable)
Workspace:       [dropdown ▾]
New session name: [e.g. WeChat Assistant  ]
[Bind]

⚠️ Important: with "New session", the session is NOT created immediately! It is created only when you send the first message to the bot in WeChat, in the selected workspace, named with the custom name you entered. If you bind and do nothing, the session will not appear anywhere — go send a message in WeChat first.

• Each WeChat chat gets its own dedicated session (UUID, never shared)
• The session is auto-attached to the selected workspace (visible in the DSH GUI workspace list after the first message)
• Subsequent messages keep flowing into the same session (conversation memory)

Mode comparison

Configuration

Method A: GUI settings (recommended) — see "Quick start". Changes take effect immediately, no restart needed.

Method B: static config in ~/.dsh/profiles/web/cordis.patch.yml:

- id: wechat-bot
  name: 'dsh-wechat-bot'
  config:
    statusPath: /wechat/status   # optional, default
    autoReply: ''                # optional: auto-reply template, supports {content} {from} (used when bridge is off)
    emptyReply: ''               # optional: fallback reply when the agent produces no text (e.g. '✅ Done'); empty = off
    bridge: true                 # optional, default true: feed WeChat messages into DSH sessions
    rootDir: '~/.dsh/proj'       # optional: workspace root (fallback for unbound chats + where new workspaces are created); default $DSH_HOME/proj, auto-created
    bindings:                    # optional: chat → workspace/session bindings
      - chatId: 'o9cq...@im.wechat'
        workspace: 'D:\proj'     # new-session mode: bind workspace (+ sessionTitle for a custom name)
      # - chatId: '...'          # or bind to an existing session (reuse its context)
      #   sessionId: 'session-xxx'

Creating workspaces / sessions

Both create under the workspace root (configurable in the settings UI, default ~/.dsh/proj, auto-created) and register it as a DSH workspace.

• Settings UI: Settings → WeChat Bot → "New workspace" card, enter a name and click "Create & bind"
• WeChat exact command "新增工作区" → the bot asks for a name → reply to create
• WeChat exact command "新增会话" → pick a workspace → reply with a name to create and name a session there (persisted, visible in the GUI workspace list):

You: 新增工作区
Bot: 📂 Please reply with the new workspace name (a same-name folder will be created under D:\proj and bound as a DSH workspace):
You: 我的项目
Bot: ✅ Workspace created: D:\proj\我的项目
     Bound as a DSH workspace — visible in the workspace list / session binding.

Names must not contain \ / : * ? " < > |; if the target folder already exists it is simply registered as a workspace (contents are untouched).

When creating sessions, the DSH default agent preset (Settings → Mode, e.g. 梁神模式) is applied automatically so tools like bash/files are available; if that preset doesn't exist on this machine, it falls back to DSH's built-in "standard" mode. Sessions created on the WeChat bridge apply the same preset.

Session bridge details

• Unbound: messages are not processed; the bot replies with a binding hint
• Bound: messages enter the bound session, agent replies go back to WeChat, and everything is written to the DSH session (visible in the GUI)
• Continuation: when bound to an existing session, replies use the full session history — everything said in the GUI is remembered; messages sent in the GUI join the same context, and later WeChat messages are answered with the latest state
• Sessions are persisted; a restart resumes them automatically, and WeChat picks up where it left off
• Set bridge: false to disable the bridge (receive/send only, no agent)

Tools

Credentials

After login, the token is stored at ~/.dsh/data/dsh-wechat-bot/accounts/<bot_id>.json.

License

MIT