npm - @wu529778790/open-im - Versions diffs - 1.9.4-beta.11 → 1.9.4-beta.12 - Mend

@wu529778790/open-im 1.9.4-beta.11 → 1.9.4-beta.12

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (3) hide show

package/README.md CHANGED Viewed

@@ -1,24 +1,25 @@
 # open-im
-[中文](./README.zh-CN.md)
+[中文文档](./README.zh-CN.md)
-Multi-platform IM bridge for AI CLI tools. Connect Telegram, Feishu, WeCom, DingTalk, QQ, and WeChat to Claude Code, Codex, and CodeBuddy so you can use your coding assistant remotely from a phone or chat window.
+Multi-platform IM bridge for AI CLI tools. Connect Telegram, Feishu, WeCom, DingTalk, QQ, and WeChat to Claude Code, Codex, and CodeBuddy — use your AI coding assistant from any phone or chat window.
 ## Features
-- Multi-platform support: Telegram, Feishu, WeCom, DingTalk, QQ, and WeChat (WorkBuddy), with multiple platforms enabled at the same time
-- Multiple AI tools: Claude, Codex, and CodeBuddy
-- Per-platform AI routing: each IM platform can use a different AI tool, with `aiCommand` as the global default and `platforms.<name>.aiCommand` as the override
-- Streaming replies: relay AI output and tool execution progress in real time (DingTalk streaming is not fully supported yet)
-- Graphical configuration page and CLI setup flow
-- Isolated sessions: each user gets an independent local session, and `/new` resets it
-- Built-in commands: `/help`, `/new`, `/cd`, `/pwd`, `/status`
+- **6 IM platforms** — Telegram, Feishu, WeCom, DingTalk, QQ, WeChat (WorkBuddy), all can run simultaneously
+- **3 AI backends** — Claude (Agent SDK), Codex, CodeBuddy
+- **Per-platform AI routing** — each IM can use a different AI tool
+- **Streaming replies** — real-time AI output and tool progress (platform-dependent)
+- **Media support** — send images, files, voice, video for AI analysis
+- **Session isolation** — independent sessions per user, `/new` to reset
+- **Web config UI** — graphical dashboard for setup and management
+- **Built-in commands** — `/help`, `/new`, `/cd`, `/pwd`, `/status`, `/allow`, `/deny`
 ## Requirements
 - Node.js >= 20
 - At least one IM platform configured
-- Authentication completed for the AI tool you want to use
+- Authentication for the AI tool you want to use
 ## Quick Start
@@ -33,114 +34,95 @@ npm install -g @wu529778790/open-im
 open-im start
 ```
-The config file is stored at `~/.open-im/config.json` by default.
+Config file: `~/.open-im/config.json`
 ## CLI Commands
-| Command           | Description                                                      |
-| ----------------- | ---------------------------------------------------------------- |
-| `open-im init`    | Initialize or append configuration without starting the service |
-| `open-im start`   | Run the service in the background                                |
-| `open-im stop`    | Stop the background service                                      |
-| `open-im dev`     | Run in the foreground for development/debugging                  |
-| `open-im dashboard` | Run only the config web UI (no bridge)                        |
+| Command             | Description                            |
+| ------------------- | -------------------------------------- |
+| `open-im init`      | Configure without starting the service |
+| `open-im start`     | Run as background service              |
+| `open-im stop`      | Stop background service                |
+| `open-im dev`       | Run in foreground (debugging)          |
+| `open-im dashboard` | Web config UI only (no bridge)         |
-## Server Deployment & Config Page
+## Web Configuration
-### Local (with browser)
+### Local
-Open the config page at [`http://127.0.0.1:39282`](http://127.0.0.1:39282) (or the URL shown after `open-im start`). The page includes:
+Open [`http://127.0.0.1:39282`](http://127.0.0.1:39282) after starting. The dashboard includes:
-- **Dashboard** – Configured / Enabled platform count and service status (Idle or Running)
-- **Platforms** – Enable and configure Telegram, Feishu, QQ, WeCom, and DingTalk (credentials, proxy, per-platform AI tool, allowed user IDs). Each platform has a “Test Configuration” button.
-- **AI Tooling** – **General**: default AI tool (Claude / Codex / CodeBuddy), work directory, hook port, log level. **Per-tool tabs**: Claude (CLI path, timeout, proxy, config path, ANTHROPIC\_\* fields), Codex (CLI path, timeout, proxy), CodeBuddy (CLI path, timeout).
-- **Service control** – Validate config, Save, Start bridge, Stop bridge.
+- **Overview** — platform count, service status
+- **Platforms** — enable and configure each IM (credentials, proxy, AI tool, allowed users)
+- **AI Tooling** — default tool, work directory, per-tool settings (CLI path, timeout, proxy, API keys)
+- **Service control** — validate, save, start/stop bridge
-WorkBuddy (WeChat) is not in the web UI; configure it in `~/.open-im/config.json` or via `open-im init`.
+> WorkBuddy (WeChat) is configured via `open-im init` or directly in `~/.open-im/config.json`.
-- `open-im start` serves both the config page and the bridge on your local machine.
-- `open-im dev` opens the page automatically only when setup is incomplete.
-- To open the page when config already exists, you can also run `open-im dashboard` to launch the config UI only (without starting the bridge).
+### Remote Server
-### Recommended server workflow
-On a remote server, the simplest and safest pattern is:
-1. **Use `dashboard` to configure via browser**
-   On the server:
-   ```bash
-   export OPEN_IM_NO_BROWSER=1
-   # Optional: bind to all interfaces if you want to open from another device
-   # export OPEN_IM_WEB_HOST=0.0.0.0
-   open-im dashboard
-   ```
-   - This starts only the config web UI (no bridge yet).
-   - If `OPEN_IM_WEB_HOST` is `0.0.0.0`, the server will print a one-time login URL like:
+```bash
+export OPEN_IM_NO_BROWSER=1
+# Optional: allow access from other devices
+# export OPEN_IM_WEB_HOST=0.0.0.0
+open-im dashboard
+```
-     ```text
-     http://your-server-ip:39282/?login_token=xxxx
-     ```
+If `OPEN_IM_WEB_HOST=0.0.0.0`, the server prints a one-time login URL:
-   - Open this URL in your browser, complete all platform/AI settings, then click **Start bridge** in the web UI.
+```
+http://your-server-ip:39282/?login_token=xxxx
+```
-2. **Run the bridge as a background service**
+Complete setup in the browser, then start the bridge:
-   After configuration is saved, you have two options:
-   - Start from the web UI: use the **Start bridge** button on the Service panel.
-   - Or start from the CLI:
+```bash
+open-im start
+```
-     ```bash
-     open-im start
-     ```
+## IM Commands
-   This runs the full bridge in the background using the saved config.
+| Command       | Description                          |
+| ------------- | ------------------------------------ |
+| `/help`       | Show help                            |
+| `/new`        | Start a new AI session               |
+| `/status`     | Show AI tool, version, session info  |
+| `/cd <path>`  | Change session working directory     |
+| `/pwd`        | Show current working directory       |
+| `/allow` `/y` | Approve a permission request         |
+| `/deny` `/n`  | Reject a permission request          |
 ## Session Behavior
-Session context is stored locally in `~/.open-im/data/sessions.json` and is separate from the IM chat history itself. Each user has an independent session directory and session metadata. Sending `/new` resets the current AI session.
+Sessions are stored locally in `~/.open-im/data/sessions.json`, separate from IM chat history. Each user gets an independent session directory. `/new` resets the AI session.
 ## Configuration
-The root-level `aiCommand` is the default AI tool for all platforms. If you want a specific IM platform to use a different tool, set `platforms.<platform>.aiCommand`.
+### Per-Platform AI Routing
-Example:
+The root-level `aiCommand` is the default AI tool. Override per-platform with `platforms.<name>.aiCommand`:
 ```json
 {
   "aiCommand": "claude",
   "platforms": {
-    "telegram": {
-      "enabled": true,
-      "aiCommand": "codex"
-    },
-    "feishu": {
-      "enabled": true,
-      "aiCommand": "codex"
-    },
-    "qq": {
-      "enabled": true,
-      "aiCommand": "codebuddy"
-    }
+    "telegram": { "enabled": true, "aiCommand": "codex" },
+    "feishu":   { "enabled": true, "aiCommand": "codex" },
+    "qq":       { "enabled": true, "aiCommand": "codebuddy" }
   }
 }
 ```
-In that setup, Telegram uses Codex, Feishu uses Codex, QQ uses CodeBuddy, and any platform without its own `aiCommand` continues using Claude.
-### Claude
+### Claude (Agent SDK)
-Claude uses the Agent SDK by default and does not depend on a local `claude` executable. In most cases you only need to provide API credentials.
-Load order:
+Claude uses the Agent SDK by default — no local `claude` executable needed. Provide API credentials:
+Credential load order:
 1. Environment variables
 2. `env` in `~/.open-im/config.json`
 3. `~/.claude/settings.json` or `~/.claude.json`
-Both the official API and compatible third-party endpoints are supported:
+Compatible with third-party endpoints:
 ```json
 {
@@ -152,47 +134,41 @@ Both the official API and compatible third-party endpoints are supported:
 }
 ```
+Claude automatically inherits plugins and settings from your local `~/.claude/settings.json`.
 ### CodeBuddy
-CodeBuddy uses the local CLI. Install it first, then either log in interactively or provide credentials through `env`.
+Install the CLI and log in:
 ```bash
 npm install -g @tencent-ai/codebuddy-code
-codebuddy --version
 codebuddy login
 ```
-Common config keys:
+Config keys:
+- `tools.codebuddy.cliPath` — CLI path (default: `codebuddy`)
+- `tools.codebuddy.skipPermissions` — skip permission prompts (default: `true`)
+- `tools.codebuddy.timeoutMs` — execution timeout (default: `600000`)
-- `tools.codebuddy.cliPath`: CLI path, defaults to `codebuddy`
-- `tools.codebuddy.skipPermissions`: whether to skip permission confirmation, defaults to `true`
-- `tools.codebuddy.timeoutMs`: total execution timeout, defaults to `600000`
-- `platforms.<platform>.aiCommand`: set to `codebuddy` if that IM platform should use CodeBuddy
+On Windows, if `cliPath` is `codebuddy`, open-im also checks `AppData\Roaming\npm\codebuddy.cmd`.
-On Windows, if `cliPath` is still `codebuddy`, open-im also tries common npm global locations such as `AppData\\Roaming\\npm\\codebuddy.cmd`.
-### Example Config File
-The following is valid JSON and can be saved directly as `~/.open-im/config.json`:
+### Example Config
 ```json
 {
   "aiCommand": "claude",
   "tools": {
     "claude": {
-      "cliPath": "claude",
-      "workDir": "D:/coding/open-im",
+      "workDir": "/path/to/project",
       "skipPermissions": true,
       "timeoutMs": 600000
     },
     "codex": {
-      "cliPath": "codex",
-      "workDir": "D:/coding/open-im",
+      "workDir": "/path/to/project",
       "skipPermissions": true,
       "proxy": "http://127.0.0.1:7890"
     },
     "codebuddy": {
-      "cliPath": "codebuddy",
       "skipPermissions": true,
       "timeoutMs": 600000
     }
@@ -200,44 +176,31 @@ The following is valid JSON and can be saved directly as `~/.open-im/config.json
   "platforms": {
     "telegram": {
       "enabled": true,
-      "aiCommand": "codex",
-      "proxy": "http://127.0.0.1:7890",
-      "allowedUserIds": [],
       "botToken": "YOUR_TELEGRAM_BOT_TOKEN"
     },
     "feishu": {
       "enabled": false,
-      "aiCommand": "codex",
-      "allowedUserIds": [],
       "appId": "YOUR_FEISHU_APP_ID",
       "appSecret": "YOUR_FEISHU_APP_SECRET"
     },
     "qq": {
       "enabled": false,
-      "aiCommand": "codebuddy",
-      "allowedUserIds": [],
       "appId": "YOUR_QQ_APP_ID",
       "secret": "YOUR_QQ_APP_SECRET"
     },
     "wework": {
       "enabled": false,
-      "aiCommand": "claude",
-      "allowedUserIds": [],
       "corpId": "YOUR_WEWORK_CORP_ID",
       "secret": "YOUR_WEWORK_SECRET"
     },
     "dingtalk": {
       "enabled": false,
-      "aiCommand": "claude",
-      "allowedUserIds": [],
       "clientId": "YOUR_DINGTALK_CLIENT_ID",
       "clientSecret": "YOUR_DINGTALK_CLIENT_SECRET",
       "cardTemplateId": "YOUR_DINGTALK_AI_CARD_TEMPLATE_ID"
     },
     "workbuddy": {
       "enabled": false,
-      "aiCommand": "claude",
-      "allowedUserIds": [],
       "accessToken": "",
       "refreshToken": "",
       "userId": ""
@@ -246,101 +209,93 @@ The following is valid JSON and can be saved directly as `~/.open-im/config.json
 }
 ```
-### Common Environment Variables
-| Variable                     | Description                                                            |
-| ---------------------------- | ---------------------------------------------------------------------- |
-| `AI_COMMAND`                 | Select `claude`, `codex`, or `codebuddy`                               |
-| `CLAUDE_WORK_DIR`            | Default session working directory                                      |
-| `LOG_DIR`                    | Log directory                                                          |
-| `LOG_LEVEL`                  | Log level                                                              |
-| `HOOK_PORT`                  | Permission service port                                                |
-| `CODEX_PROXY`                | Proxy used by Codex to access `chatgpt.com`                            |
-| `OPENAI_API_KEY`             | Codex API key, can replace `codex login`                               |
-| `CODEBUDDY_CLI_PATH`         | Override CodeBuddy CLI path                                            |
-| `CODEBUDDY_TIMEOUT_MS`       | Override CodeBuddy timeout                                             |
-| `CODEBUDDY_SKIP_PERMISSIONS` | Override CodeBuddy skip-permissions behavior                           |
-| `CODEBUDDY_IDLE_TIMEOUT_MS`  | Abort CodeBuddy when it stays silent for too long                      |
-| `CODEBUDDY_API_KEY`          | CodeBuddy API key, can replace `codebuddy login`                       |
-| `CODEBUDDY_AUTH_TOKEN`       | CodeBuddy auth token, can replace `codebuddy login`                    |
-| `TELEGRAM_BOT_TOKEN`         | Telegram bot token                                                     |
-| `TELEGRAM_PROXY`             | Telegram proxy URL                                                     |
-| `TELEGRAM_ALLOWED_USER_IDS`  | Telegram allowlist                                                     |
-| `FEISHU_APP_ID`              | Feishu app ID                                                          |
-| `FEISHU_APP_SECRET`          | Feishu app secret                                                      |
-| `FEISHU_ALLOWED_USER_IDS`    | Feishu allowlist                                                       |
-| `QQ_BOT_APPID`               | QQ bot app ID                                                          |
-| `QQ_BOT_SECRET`              | QQ bot app secret                                                      |
-| `QQ_BOT_SANDBOX`             | QQ bot sandbox mode (`1` / `true` to enable, disabled by default)      |
-| `QQ_ALLOWED_USER_IDS`        | QQ allowlist                                                           |
-| `DINGTALK_CLIENT_ID`         | DingTalk client ID / AppKey                                            |
-| `DINGTALK_CLIENT_SECRET`     | DingTalk client secret / AppSecret                                     |
-| `DINGTALK_CARD_TEMPLATE_ID`  | DingTalk AI card template ID; enables single-message streaming replies |
-| `DINGTALK_ALLOWED_USER_IDS`  | DingTalk allowlist                                                     |
-| `WEWORK_CORP_ID`             | WeCom bot ID                                                           |
-| `WEWORK_SECRET`              | WeCom secret                                                           |
-| `WEWORK_WS_URL`              | WeCom WebSocket URL                                                    |
-| `WEWORK_ALLOWED_USER_IDS`    | WeCom allowlist                                                        |
-| `WORKBUDDY_ACCESS_TOKEN`     | WorkBuddy OAuth access token (auto-generated by `open-im init`)        |
-| `WORKBUDDY_REFRESH_TOKEN`    | WorkBuddy OAuth refresh token (auto-generated by `open-im init`)       |
-| `WORKBUDDY_USER_ID`          | WorkBuddy user ID                                                      |
-| `WORKBUDDY_BASE_URL`         | WorkBuddy API base URL, defaults to `https://copilot.tencent.com`      |
-| `WORKBUDDY_GUID`             | WorkBuddy connection GUID (optional)                                   |
-| `WORKBUDDY_WORKSPACE_PATH`   | WorkBuddy workspace path (optional)                                    |
-| `WORKBUDDY_ALLOWED_USER_IDS` | WorkBuddy allowlist                                                    |
-### Platform Setup Sources
-- Telegram: get the bot token from [@BotFather](https://t.me/BotFather)
-- Feishu: create an app and enable the bot in the [Feishu Open Platform](https://open.feishu.cn/)
-- QQ: create a bot in the [QQ Open Platform](https://bot.q.qq.com/) and get the `App ID` and `App Secret`
-- DingTalk: create an internal enterprise app in DingTalk Open Platform, enable bot Stream Mode, and get the `Client ID` and `Client Secret`
-- WeCom: get the bot ID and secret from the [WeCom admin console](https://work.weixin.qq.com/)
-- WeChat (WorkBuddy): connects via CodeBuddy (copilot.tencent.com) Centrifuge WebSocket; run `open-im init` and select "WorkBuddy 微信客服 (WeChat KF)" to complete OAuth login and WeChat KF binding
-Notes on DingTalk: the current implementation uses a hybrid model of "Stream Mode for receiving messages + OpenAPI for sending messages".
-- Plain text replies in a session are sent through `sessionWebhook`
-- If `cardTemplateId` is configured, the app will try AI assistant `prepare/update/finish` streaming cards; if that fails, it falls back to plain text. In custom bot or regular group scenarios, the interactive card API may return `param.error`, so single-message streaming updates are not available there yet
-- Startup and shutdown notifications are not sent to DingTalk (the OpenAPI robot API does not support proactive messages in the same way). Other platforms (e.g. Telegram, Feishu, WeCom) still receive lifecycle notifications when configured
-DingTalk AI card templates are already compatible with the official "Search Result Card" template and use the variables `lastMessage`, `content`, `resources`, `users`, and `flowStatus`. If you use that template, no template changes are required for streaming updates.
-## IM Commands
-| Command       | Description                                              |
-| ------------- | -------------------------------------------------------- |
-| `/help`       | Show help                                                |
-| `/new`        | Start a new session                                      |
-| `/status`     | Show AI tool, version, session directory, and session ID |
-| `/cd <path>`  | Change the session working directory                     |
-| `/pwd`        | Show the current session working directory               |
-| `/allow` `/y` | Approve a permission request                             |
-| `/deny` `/n`  | Reject a permission request                              |
+### Environment Variables
+#### General
+| Variable            | Description                                    |
+| ------------------- | ---------------------------------------------- |
+| `AI_COMMAND`        | Default AI tool (`claude` / `codex` / `codebuddy`) |
+| `CLAUDE_WORK_DIR`   | Default session working directory              |
+| `LOG_DIR`           | Log directory                                  |
+| `LOG_LEVEL`         | Log level                                      |
+| `HOOK_PORT`         | Permission service port                        |
+#### AI Tool Credentials
+| Variable                     | Description                                |
+| ---------------------------- | ------------------------------------------ |
+| `ANTHROPIC_API_KEY`          | Claude API key                             |
+| `ANTHROPIC_AUTH_TOKEN`       | Claude OAuth token                         |
+| `ANTHROPIC_BASE_URL`         | Claude API base URL                        |
+| `ANTHROPIC_MODEL`            | Claude model name                          |
+| `OPENAI_API_KEY`             | Codex API key                              |
+| `CODEX_PROXY`                | Codex proxy for `chatgpt.com`              |
+| `CODEBUDDY_CLI_PATH`         | CodeBuddy CLI path                         |
+| `CODEBUDDY_TIMEOUT_MS`       | CodeBuddy timeout                          |
+| `CODEBUDDY_API_KEY`          | CodeBuddy API key                          |
+| `CODEBUDDY_AUTH_TOKEN`       | CodeBuddy auth token                       |
+#### Platform Credentials
+| Variable                     | Description                                |
+| ---------------------------- | ------------------------------------------ |
+| `TELEGRAM_BOT_TOKEN`         | Telegram bot token                         |
+| `TELEGRAM_PROXY`             | Telegram proxy URL                         |
+| `TELEGRAM_ALLOWED_USER_IDS`  | Telegram allowed user IDs                  |
+| `FEISHU_APP_ID`              | Feishu app ID                              |
+| `FEISHU_APP_SECRET`          | Feishu app secret                          |
+| `FEISHU_ALLOWED_USER_IDS`    | Feishu allowed user IDs                    |
+| `QQ_BOT_APPID`               | QQ bot app ID                              |
+| `QQ_BOT_SECRET`              | QQ bot app secret                          |
+| `QQ_BOT_SANDBOX`             | QQ sandbox mode (`1` / `true`)             |
+| `QQ_ALLOWED_USER_IDS`        | QQ allowed user IDs                        |
+| `DINGTALK_CLIENT_ID`         | DingTalk client ID / AppKey                |
+| `DINGTALK_CLIENT_SECRET`     | DingTalk client secret / AppSecret         |
+| `DINGTALK_CARD_TEMPLATE_ID`  | DingTalk AI card template ID               |
+| `DINGTALK_ALLOWED_USER_IDS`  | DingTalk allowed user IDs                  |
+| `WEWORK_CORP_ID`             | WeCom bot ID                               |
+| `WEWORK_SECRET`              | WeCom secret                               |
+| `WEWORK_WS_URL`              | WeCom WebSocket URL                        |
+| `WEWORK_ALLOWED_USER_IDS`    | WeCom allowed user IDs                     |
+| `WORKBUDDY_ACCESS_TOKEN`     | WorkBuddy OAuth access token               |
+| `WORKBUDDY_REFRESH_TOKEN`    | WorkBuddy OAuth refresh token              |
+| `WORKBUDDY_USER_ID`          | WorkBuddy user ID                          |
+| `WORKBUDDY_BASE_URL`         | WorkBuddy API base URL                     |
+| `WORKBUDDY_ALLOWED_USER_IDS` | WorkBuddy allowed user IDs                 |
+### Platform Setup
+| Platform  | Setup source                                                    |
+| --------- | --------------------------------------------------------------- |
+| Telegram  | [@BotFather](https://t.me/BotFather)                           |
+| Feishu    | [Feishu Open Platform](https://open.feishu.cn/)                |
+| QQ        | [QQ Open Platform](https://bot.q.qq.com/)                      |
+| DingTalk  | DingTalk Open Platform — enable bot Stream Mode                |
+| WeCom     | [WeCom admin console](https://work.weixin.qq.com/)             |
+| WeChat    | Run `open-im init` and select "WorkBuddy" for OAuth + binding  |
+**DingTalk notes:**
+- Uses Stream Mode (receive) + OpenAPI (send)
+- With `cardTemplateId`: AI assistant streaming cards; falls back to plain text on failure
+- Custom bots and regular groups only support single text replies
+- Startup/shutdown notifications are not sent to DingTalk
 ## Troubleshooting
-**Telegram does not respond**: check network access. If needed, add `"proxy": "http://127.0.0.1:7890"` to the Telegram platform config or set `TELEGRAM_PROXY`.
-**QQ cannot connect**: make sure the bot has been created and enabled in QQ Open Platform, then verify `QQ_BOT_APPID`, `QQ_BOT_SECRET`, or `platforms.qq`.
-**QQ sends duplicate replies**: update to the latest version. This issue was fixed recently.
-**Feishu card errors**: if card callbacks are not configured, you can use `/mode ask` or `/mode yolo` directly.
-**WeCom notifications are not received**: the bot must receive at least one message first before it can send proactive notifications.
-**DingTalk cannot reply**: make sure bot Stream Mode is enabled for the app, then verify `DINGTALK_CLIENT_ID`, `DINGTALK_CLIENT_SECRET`, or `platforms.dingtalk`.
-**DingTalk has no streaming updates**: when `prepare` fails, the app falls back to plain text replies. In custom bot or regular group scenarios, neither the AI assistant API nor the interactive card API is available, so only single plain text replies are supported.
-**Codex shows `stream disconnected` or `error sending request`**: `chatgpt.com` is not reachable. Configure `tools.codex.proxy` or set `CODEX_PROXY`.
-**CodeBuddy prompts for login**: run `codebuddy login` first. `open-im` does not read CodeBuddy login state from `~/.open-im/config.json`.
-**WorkBuddy cannot connect**: run `open-im init` to re-authenticate. Tokens may expire — the client will attempt auto-reconnect, but if the refresh token is invalid, a fresh login is required.
-**WorkBuddy WeChat KF not receiving messages**: ensure the WeChat KF binding was completed during `open-im init`. You can re-run init to generate a new binding link.
+| Issue | Solution |
+| ----- | -------- |
+| Telegram not responding | Check network, add `proxy` or set `TELEGRAM_PROXY` |
+| QQ cannot connect | Verify bot is created and `QQ_BOT_APPID` / `QQ_BOT_SECRET` are correct |
+| QQ duplicate replies | Update to latest version |
+| Feishu card errors | Use `/mode ask` or `/mode yolo` without card callbacks |
+| WeCom no notifications | Send at least one message to the bot first |
+| DingTalk cannot reply | Verify Stream Mode is enabled and credentials are correct |
+| DingTalk no streaming | Custom bots only support plain text; configure `cardTemplateId` for AI assistant streaming |
+| Codex `stream disconnected` | Configure `tools.codex.proxy` or `CODEX_PROXY` for `chatgpt.com` access |
+| CodeBuddy asks for login | Run `codebuddy login` first |
+| WorkBuddy cannot connect | Run `open-im init` to re-authenticate; tokens may expire |
+| WorkBuddy WeChat not receiving | Re-run `open-im init` to generate new WeChat KF binding link |
 ## License

package/README.zh-CN.md CHANGED Viewed

@@ -2,17 +2,18 @@
 [English](./README.md)
-多平台 IM 桥接工具，把 Telegram、飞书、企业微信、钉钉、QQ、微信接到 AI CLI 工具（Claude Code、Codex、CodeBuddy），方便在手机或聊天窗口里远程使用 AI 编程助手。
+多平台 IM 桥接工具，把 Telegram、飞书、企业微信、钉钉、QQ、微信接到 AI CLI 工具（Claude Code、Codex、CodeBuddy），在手机或聊天窗口远程使用 AI 编程助手。
 ## 功能特性
-- 多平台：支持 Telegram、飞书、企业微信、钉钉、QQ、微信（WorkBuddy），可同时启用
-- 多 AI 工具：支持 Claude、Codex、CodeBuddy
-- 按平台分配 AI：根级 `aiCommand` 作为默认值，`platforms.<name>.aiCommand` 可为不同 IM 单独指定 AI 工具
-- 流式输出：实时回传 AI 回复与工具执行进度（目前钉钉暂未实现流式传输）
-- 图形化配置页面 / CLI 配置引导
-- 会话隔离：每个用户独立维护本地会话，`/new` 可重置
-- 常用命令：支持 `/help`、`/new`、`/cd`、`/pwd`、`/status`
+- **6 个 IM 平台** — Telegram、飞书、企业微信、钉钉、QQ、微信（WorkBuddy），可同时启用
+- **3 种 AI 后端** — Claude（Agent SDK）、Codex、CodeBuddy
+- **按平台分配 AI** — 每个 IM 平台可以使用不同的 AI 工具
+- **流式输出** — 实时回传 AI 回复与工具执行进度（因平台而异）
+- **多媒体支持** — 支持发送图片、文件、语音、视频进行 AI 分析
+- **会话隔离** — 每个用户独立维护本地会话，`/new` 可重置
+- **Web 配置页面** — 图形化仪表板，在线管理配置
+- **内置命令** — `/help`、`/new`、`/cd`、`/pwd`、`/status`、`/allow`、`/deny`
 ## 环境要求
@@ -33,120 +34,95 @@ npm install -g @wu529778790/open-im
 open-im start
 ```
-配置文件默认保存在 `~/.open-im/config.json`。
+配置文件：`~/.open-im/config.json`
 ## CLI 命令
-| 命令              | 说明                           |
-| ----------------- | ------------------------------ |
-| `open-im init`    | 初始化或追加配置，不启动服务   |
-| `open-im start`   | 后台运行服务                   |
-| `open-im stop`    | 停止后台服务                   |
-| `open-im dev`     | 前台运行（调试模式）           |
-| `open-im dashboard` | 仅启动 Web 配置页（不启动桥接服务） |
+| 命令                | 说明                           |
+| ------------------- | ------------------------------ |
+| `open-im init`      | 配置平台和 AI 工具，不启动服务 |
+| `open-im start`     | 后台运行服务                   |
+| `open-im stop`      | 停止后台服务                   |
+| `open-im dev`       | 前台运行（调试模式）           |
+| `open-im dashboard` | 仅启动 Web 配置页（不启动桥接）|
-## 服务器部署与图形化配置
+## Web 配置页面
-### 本机（带浏览器）使用
+### 本机使用
-在本机直接运行：
+启动后打开 [`http://127.0.0.1:39282`](http://127.0.0.1:39282)，页面包括：
-```bash
-open-im start
-```
-然后在浏览器中打开 [`http://127.0.0.1:39282`](http://127.0.0.1:39282)（或命令行里提示的地址），页面结构如下：
-- **概览** – 已配置/已启用平台数量、服务状态（未启动或运行中）
-- **平台配置** – 启用并填写 Telegram、飞书、QQ、企业微信、钉钉的凭证（Bot Token/App ID/Secret、代理、该平台使用的 AI 工具、白名单用户 ID）。每个平台提供「校验配置」按钮
-- **AI 工具配置** – **公共**：默认 AI 工具（Claude / Codex / CodeBuddy）、工作目录、Hook 端口、日志级别。**分工具**：Claude（CLI 路径、超时、代理、配置路径、ANTHROPIC\_\* 等）、Codex（CLI 路径、超时、代理）、CodeBuddy（CLI 路径、超时）
-- **服务控制** – 校验配置、保存、启动桥接、停止桥接
-WorkBuddy（微信）暂不在网页中配置，如需使用请在 `~/.open-im/config.json` 中手动配置或通过 `open-im init` 引导。
+- **概览** — 已配置/已启用平台数量、服务状态
+- **平台配置** — 启用并填写各 IM 的凭证（Token/App ID/Secret、代理、AI 工具、白名单）
+- **AI 工具配置** — 默认 AI 工具、工作目录、各工具单独设置（CLI 路径、超时、代理、API Key）
+- **服务控制** — 校验配置、保存、启动/停止桥接
-- `open-im start` 会同时启动桥接服务并提供该配置页（本机场景）。
-- `open-im dev` 仅在未完成配置时自动打开页面。
-- 已有配置但想单独打开配置页时，可以使用 `open-im dashboard` 启动仅 Web 配置服务。
+> WorkBuddy（微信）通过 `open-im init` 或直接编辑 `~/.open-im/config.json` 配置。
-### 推荐的服务器端使用方式
+### 远程服务器
-在远程服务器上，建议的最简单、安全的方式是：
-1. **先通过 `dashboard` 在浏览器里完成配置**
-   在服务器上执行：
-   ```bash
-   export OPEN_IM_NO_BROWSER=1
-   # 可选：如果希望从其他设备访问配置页，可以绑定到所有网卡
-   # export OPEN_IM_WEB_HOST=0.0.0.0
-   open-im dashboard
-   ```
-   - 这只会启动 Web 配置页，不会同时启动桥接服务。
-   - 若设置了 `OPEN_IM_WEB_HOST=0.0.0.0`，服务端会输出一次性登录链接，例如：
+```bash
+export OPEN_IM_NO_BROWSER=1
+# 可选：允许从其他设备访问配置页
+# export OPEN_IM_WEB_HOST=0.0.0.0
+open-im dashboard
+```
-     ```text
-     http://your-server-ip:39282/?login_token=xxxx
-     ```
+若设置了 `OPEN_IM_WEB_HOST=0.0.0.0`，服务端会输出一次性登录链接：
-   - 在浏览器中打开该链接，按照页面提示完成各个平台 / AI 工具配置，最后在页面中点击 **「Start bridge」** 按钮启动桥接服务。
+```
+http://your-server-ip:39282/?login_token=xxxx
+```
-2. **后台运行桥接服务**
+在浏览器中完成配置后，启动桥接服务：
-   配置保存后，有两种启动方式：
-   - 在 Web 页面 Service 面板中直接点击 **「Start bridge」**；
-   - 或者在服务器上运行：
+```bash
+open-im start
+```
-     ```bash
-     open-im start
-     ```
+## IM 内命令
-   这会根据已保存的配置，在后台长期运行桥接服务。
+| 命令          | 说明                   |
+| ------------- | ---------------------- |
+| `/help`       | 显示帮助               |
+| `/new`        | 开始新的 AI 会话       |
+| `/status`     | 显示 AI 工具和会话信息 |
+| `/cd <路径>`  | 切换会话目录           |
+| `/pwd`        | 显示当前会话目录       |
+| `/allow` `/y` | 允许权限请求           |
+| `/deny` `/n`  | 拒绝权限请求           |
 ## 会话说明
-会话上下文保存在本地 `~/.open-im/data/sessions.json`，与 IM 聊天记录本身无关。每个用户有独立会话目录和 session 信息，发送 `/new` 会重置当前 AI 会话。
+会话保存在本地 `~/.open-im/data/sessions.json`，与 IM 聊天记录无关。每个用户有独立的会话目录。`/new` 重置当前 AI 会话。
 ## 配置说明
-根级 `aiCommand` 是所有平台共用的默认 AI 工具。若某个 IM 平台需要单独绑定其他工具，可以设置 `platforms.<platform>.aiCommand`。
+### 按平台分配 AI 工具
-示例：
+根级 `aiCommand` 是默认 AI 工具，可通过 `platforms.<name>.aiCommand` 为不同 IM 单独指定：
 ```json
 {
   "aiCommand": "claude",
   "platforms": {
-    "telegram": {
-      "enabled": true,
-      "aiCommand": "codex"
-    },
-    "feishu": {
-      "enabled": true,
-      "aiCommand": "codex"
-    },
-    "qq": {
-      "enabled": true,
-      "aiCommand": "codebuddy"
-    }
+    "telegram": { "enabled": true, "aiCommand": "codex" },
+    "feishu":   { "enabled": true, "aiCommand": "codex" },
+    "qq":       { "enabled": true, "aiCommand": "codebuddy" }
   }
 }
 ```
-这个配置下，Telegram 会走 Codex，飞书会走 Codex，QQ 会走 CodeBuddy，其他未单独指定 `aiCommand` 的平台仍然使用 Claude。
+### Claude（Agent SDK）
-### Claude
-Claude 默认使用 Agent SDK，不依赖本地 `claude` 可执行文件；通常只需要配置 API 凭证。
-自动加载顺序：
+Claude 默认使用 Agent SDK，不需要本地 `claude` 可执行文件，只需配置 API 凭证。
+凭证加载顺序：
 1. 环境变量
 2. `~/.open-im/config.json` 的 `env`
 3. `~/.claude/settings.json` 或 `~/.claude.json`
-支持官方 API，也支持第三方兼容接口：
+支持第三方兼容接口：
 ```json
 {
@@ -158,47 +134,41 @@ Claude 默认使用 Agent SDK，不依赖本地 `claude` 可执行文件；通
 }
 ```
+Claude 会自动继承本地 `~/.claude/settings.json` 中的插件和配置。
 ### CodeBuddy
-CodeBuddy 依赖本地 CLI。先安装 CLI，再通过交互登录或在 `env` 中提供凭证。
+安装 CLI 并登录：
 ```bash
 npm install -g @tencent-ai/codebuddy-code
-codebuddy --version
 codebuddy login
 ```
-常用配置项：
+配置项：
+- `tools.codebuddy.cliPath` — CLI 路径（默认：`codebuddy`）
+- `tools.codebuddy.skipPermissions` — 跳过权限确认（默认：`true`）
+- `tools.codebuddy.timeoutMs` — 执行超时（默认：`600000`）
-- `tools.codebuddy.cliPath`：CLI 路径，默认 `codebuddy`
-- `tools.codebuddy.skipPermissions`：是否跳过权限确认，默认 `true`
-- `tools.codebuddy.timeoutMs`：总执行超时，默认 `600000`
-- `platforms.<platform>.aiCommand`：若某个平台要走 CodeBuddy，可设为 `codebuddy`
-在 Windows 上，如果 `cliPath` 仍然是 `codebuddy`，open-im 还会自动尝试 `AppData\\Roaming\\npm\\codebuddy.cmd` 等常见全局安装路径。
+Windows 上若 `cliPath` 为 `codebuddy`，会自动尝试 `AppData\Roaming\npm\codebuddy.cmd`。
 ### 配置文件示例
-下面示例是合法 JSON，可直接保存为 `~/.open-im/config.json`：
 ```json
 {
   "aiCommand": "claude",
   "tools": {
     "claude": {
-      "cliPath": "claude",
-      "workDir": "D:/coding/open-im",
+      "workDir": "/path/to/project",
       "skipPermissions": true,
       "timeoutMs": 600000
     },
     "codex": {
-      "cliPath": "codex",
-      "workDir": "D:/coding/open-im",
+      "workDir": "/path/to/project",
       "skipPermissions": true,
       "proxy": "http://127.0.0.1:7890"
     },
     "codebuddy": {
-      "cliPath": "codebuddy",
       "skipPermissions": true,
       "timeoutMs": 600000
     }
@@ -206,44 +176,31 @@ codebuddy login
   "platforms": {
     "telegram": {
       "enabled": true,
-      "aiCommand": "codex",
-      "proxy": "http://127.0.0.1:7890",
-      "allowedUserIds": [],
       "botToken": "YOUR_TELEGRAM_BOT_TOKEN"
     },
     "feishu": {
       "enabled": false,
-      "aiCommand": "codex",
-      "allowedUserIds": [],
       "appId": "YOUR_FEISHU_APP_ID",
       "appSecret": "YOUR_FEISHU_APP_SECRET"
     },
     "qq": {
       "enabled": false,
-      "aiCommand": "codebuddy",
-      "allowedUserIds": [],
       "appId": "YOUR_QQ_APP_ID",
       "secret": "YOUR_QQ_APP_SECRET"
     },
     "wework": {
       "enabled": false,
-      "aiCommand": "claude",
-      "allowedUserIds": [],
       "corpId": "YOUR_WEWORK_CORP_ID",
       "secret": "YOUR_WEWORK_SECRET"
     },
     "dingtalk": {
       "enabled": false,
-      "aiCommand": "claude",
-      "allowedUserIds": [],
       "clientId": "YOUR_DINGTALK_CLIENT_ID",
       "clientSecret": "YOUR_DINGTALK_CLIENT_SECRET",
       "cardTemplateId": "YOUR_DINGTALK_AI_CARD_TEMPLATE_ID"
     },
     "workbuddy": {
       "enabled": false,
-      "aiCommand": "claude",
-      "allowedUserIds": [],
       "accessToken": "",
       "refreshToken": "",
       "userId": ""
@@ -252,101 +209,93 @@ codebuddy login
 }
 ```
-### 常用环境变量
-| 变量                         | 说明                                           |
-| ---------------------------- | ---------------------------------------------- |
-| `AI_COMMAND`                 | 选择 `claude` / `codex` / `codebuddy`          |
-| `CLAUDE_WORK_DIR`            | 默认会话目录                                   |
-| `LOG_DIR`                    | 日志目录                                       |
-| `LOG_LEVEL`                  | 日志级别                                       |
-| `HOOK_PORT`                  | 权限服务端口                                   |
-| `CODEX_PROXY`                | Codex 访问 `chatgpt.com` 的代理                |
-| `OPENAI_API_KEY`             | Codex API Key，可替代 `codex login`            |
-| `CODEBUDDY_CLI_PATH`         | 覆盖 CodeBuddy CLI 路径                        |
-| `CODEBUDDY_TIMEOUT_MS`       | 覆盖 CodeBuddy 超时                            |
-| `CODEBUDDY_SKIP_PERMISSIONS` | 覆盖 CodeBuddy 的跳过权限确认行为              |
-| `CODEBUDDY_IDLE_TIMEOUT_MS`  | CodeBuddy 长时间无输出时自动终止               |
-| `CODEBUDDY_API_KEY`          | CodeBuddy API Key，可替代 `codebuddy login`    |
-| `CODEBUDDY_AUTH_TOKEN`       | CodeBuddy Auth Token，可替代 `codebuddy login` |
-| `TELEGRAM_BOT_TOKEN`         | Telegram Bot Token                             |
-| `TELEGRAM_PROXY`             | Telegram 代理地址                              |
-| `TELEGRAM_ALLOWED_USER_IDS`  | Telegram 白名单                                |
-| `FEISHU_APP_ID`              | 飞书 App ID                                    |
-| `FEISHU_APP_SECRET`          | 飞书 App Secret                                |
-| `FEISHU_ALLOWED_USER_IDS`    | 飞书白名单                                     |
-| `QQ_BOT_APPID`               | QQ 机器人 App ID                               |
-| `QQ_BOT_SECRET`              | QQ 机器人 App Secret                           |
-| `QQ_BOT_SANDBOX`             | QQ 机器人沙箱模式（`1`/`true` 启用，默认关闭） |
-| `QQ_ALLOWED_USER_IDS`        | QQ 白名单                                      |
-| `DINGTALK_CLIENT_ID`         | 钉钉应用 Client ID / AppKey                    |
-| `DINGTALK_CLIENT_SECRET`     | 钉钉应用 Client Secret / AppSecret             |
-| `DINGTALK_CARD_TEMPLATE_ID`  | 钉钉 AI 卡片模板 ID，配置后启用单条流式回复    |
-| `DINGTALK_ALLOWED_USER_IDS`  | 钉钉白名单                                     |
-| `WEWORK_CORP_ID`             | 企业微信 Bot ID                                |
-| `WEWORK_SECRET`              | 企业微信 Secret                                |
-| `WEWORK_WS_URL`              | 企业微信 WebSocket 地址                        |
-| `WEWORK_ALLOWED_USER_IDS`    | 企业微信白名单                                 |
-| `WORKBUDDY_ACCESS_TOKEN`     | WorkBuddy OAuth 访问令牌（由 `open-im init` 自动生成） |
-| `WORKBUDDY_REFRESH_TOKEN`    | WorkBuddy OAuth 刷新令牌（由 `open-im init` 自动生成） |
-| `WORKBUDDY_USER_ID`          | WorkBuddy 用户 ID                              |
-| `WORKBUDDY_BASE_URL`         | WorkBuddy API 地址，默认 `https://copilot.tencent.com` |
-| `WORKBUDDY_GUID`             | WorkBuddy 连接 GUID（可选）                    |
-| `WORKBUDDY_WORKSPACE_PATH`   | WorkBuddy 工作区路径（可选）                   |
-| `WORKBUDDY_ALLOWED_USER_IDS` | WorkBuddy 白名单                               |
+### 环境变量
+#### 通用
+| 变量              | 说明                                       |
+| ----------------- | ------------------------------------------ |
+| `AI_COMMAND`      | 默认 AI 工具（`claude` / `codex` / `codebuddy`）|
+| `CLAUDE_WORK_DIR` | 默认会话工作目录                           |
+| `LOG_DIR`         | 日志目录                                   |
+| `LOG_LEVEL`       | 日志级别                                   |
+| `HOOK_PORT`       | 权限服务端口                               |
+#### AI 工具凭证
+| 变量                         | 说明                          |
+| ---------------------------- | ----------------------------- |
+| `ANTHROPIC_API_KEY`          | Claude API Key                |
+| `ANTHROPIC_AUTH_TOKEN`       | Claude OAuth Token            |
+| `ANTHROPIC_BASE_URL`         | Claude API 地址               |
+| `ANTHROPIC_MODEL`            | Claude 模型名称               |
+| `OPENAI_API_KEY`             | Codex API Key                 |
+| `CODEX_PROXY`                | Codex 访问 `chatgpt.com` 的代理|
+| `CODEBUDDY_CLI_PATH`         | CodeBuddy CLI 路径            |
+| `CODEBUDDY_TIMEOUT_MS`       | CodeBuddy 超时                |
+| `CODEBUDDY_API_KEY`          | CodeBuddy API Key             |
+| `CODEBUDDY_AUTH_TOKEN`       | CodeBuddy Auth Token          |
+#### 平台凭证
+| 变量                         | 说明                          |
+| ---------------------------- | ----------------------------- |
+| `TELEGRAM_BOT_TOKEN`         | Telegram Bot Token            |
+| `TELEGRAM_PROXY`             | Telegram 代理地址             |
+| `TELEGRAM_ALLOWED_USER_IDS`  | Telegram 白名单               |
+| `FEISHU_APP_ID`              | 飞书 App ID                   |
+| `FEISHU_APP_SECRET`          | 飞书 App Secret               |
+| `FEISHU_ALLOWED_USER_IDS`    | 飞书白名单                    |
+| `QQ_BOT_APPID`               | QQ 机器人 App ID              |
+| `QQ_BOT_SECRET`              | QQ 机器人 App Secret          |
+| `QQ_BOT_SANDBOX`             | QQ 沙箱模式（`1`/`true`）     |
+| `QQ_ALLOWED_USER_IDS`        | QQ 白名单                     |
+| `DINGTALK_CLIENT_ID`         | 钉钉应用 Client ID / AppKey   |
+| `DINGTALK_CLIENT_SECRET`     | 钉钉应用 Client Secret        |
+| `DINGTALK_CARD_TEMPLATE_ID`  | 钉钉 AI 卡片模板 ID           |
+| `DINGTALK_ALLOWED_USER_IDS`  | 钉钉白名单                    |
+| `WEWORK_CORP_ID`             | 企业微信 Bot ID               |
+| `WEWORK_SECRET`              | 企业微信 Secret               |
+| `WEWORK_WS_URL`              | 企业微信 WebSocket 地址       |
+| `WEWORK_ALLOWED_USER_IDS`    | 企业微信白名单                |
+| `WORKBUDDY_ACCESS_TOKEN`     | WorkBuddy OAuth 访问令牌      |
+| `WORKBUDDY_REFRESH_TOKEN`    | WorkBuddy OAuth 刷新令牌      |
+| `WORKBUDDY_USER_ID`          | WorkBuddy 用户 ID             |
+| `WORKBUDDY_BASE_URL`         | WorkBuddy API 地址            |
+| `WORKBUDDY_ALLOWED_USER_IDS` | WorkBuddy 白名单              |
 ### 平台配置来源
-- Telegram：从 [@BotFather](https://t.me/BotFather) 获取 Bot Token
-- 飞书：从 [飞书开放平台](https://open.feishu.cn/) 创建应用并启用机器人
-- QQ：从 [QQ 开放平台](https://bot.q.qq.com/) 创建机器人，获取 `App ID` 和 `App Secret`
-- 钉钉：从钉钉开放平台创建企业内部应用，启用机器人 Stream Mode，获取 `Client ID` 和 `Client Secret`
-- 企业微信：从 [企业微信管理后台](https://work.weixin.qq.com/) 获取 Bot ID 和 Secret
-- 微信（WorkBuddy）：通过 CodeBuddy（copilot.tencent.com）Centrifuge WebSocket 接入微信客服；运行 `open-im init` 并选择 "WorkBuddy 微信客服 (WeChat KF)" 完成 OAuth 登录和微信客服绑定
-说明：钉钉当前采用“Stream Mode 收消息 + OpenAPI 发送消息”的混合模式。
-- 会话内普通文本回复默认走 `sessionWebhook`
-- 若配置了 `cardTemplateId`，会尝试 AI 助理 `prepare/update/finish` 流式卡片；失败则 fallback 为普通文本（自定义机器人/普通群场景下互动卡片 API 报 `param.error`，暂不支持单条流式更新）
-- 启动/关闭通知不会发给钉钉（OpenAPI 机器人接口不支持主动发消息）；其他已配置平台（如 Telegram、飞书、企业微信）仍会收到生命周期通知
-钉钉 AI 卡片模板：已适配官方「搜索结果卡片」模板，使用变量 `lastMessage`、`content`、`resources`、`users`、`flowStatus`。若使用该模板，无需修改模板即可实现流式更新。
-## IM 内命令
-| 命令          | 说明                                  |
-| ------------- | ------------------------------------- |
-| `/help`       | 显示帮助                              |
-| `/new`        | 开始新会话                            |
-| `/status`     | 显示 AI 工具、版本、会话目录、会话 ID |
-| `/cd <路径>`  | 切换会话目录                          |
-| `/pwd`        | 显示当前会话目录                      |
-| `/allow` `/y` | 允许权限请求                          |
-| `/deny` `/n`  | 拒绝权限请求                          |
+| 平台     | 配置来源                                                        |
+| -------- | --------------------------------------------------------------- |
+| Telegram | 从 [@BotFather](https://t.me/BotFather) 获取 Bot Token         |
+| 飞书     | 从 [飞书开放平台](https://open.feishu.cn/) 创建应用并启用机器人 |
+| QQ       | 从 [QQ 开放平台](https://bot.q.qq.com/) 创建机器人              |
+| 钉钉     | 从钉钉开放平台创建应用，启用机器人 Stream Mode                  |
+| 企业微信 | 从 [企业微信管理后台](https://work.weixin.qq.com/) 获取凭证     |
+| 微信     | 运行 `open-im init` 并选择 "WorkBuddy" 完成 OAuth 登录和绑定   |
+**钉钉说明：**
+- 采用 Stream Mode 收消息 + OpenAPI 发消息的混合模式
+- 配置 `cardTemplateId` 后启用 AI 助理流式卡片，失败时回退为纯文本
+- 自定义机器人和普通群仅支持单条文本回复
+- 启动/关闭通知不会发送到钉钉
 ## 故障排除
-**Telegram 无响应**：检查网络，必要时在 Telegram 平台配置中添加 `"proxy": "http://127.0.0.1:7890"` 或设置 `TELEGRAM_PROXY`。
-**QQ 无法连接**：确认机器人已在 QQ 开放平台创建并启用，检查 `QQ_BOT_APPID`、`QQ_BOT_SECRET` 或 `platforms.qq` 配置是否正确。
-**QQ 重复回复**：如遇到消息重复发送，请确保使用最新版本，该问题已在近期修复。
-**飞书卡片报错**：未配置卡片回调时，可直接用 `/mode ask`、`/mode yolo`。
-**企业微信收不到通知**：需要先给机器人发过一条消息，后续才能收到主动通知。
-**钉钉无法回复**：确认应用已启用机器人 Stream Mode，并检查 `DINGTALK_CLIENT_ID`、`DINGTALK_CLIENT_SECRET` 或 `platforms.dingtalk` 配置是否正确。
-**钉钉没有流式更新**：`prepare` 失败时 fallback 为普通文本回复。自定义机器人/普通群场景下，AI 助理和互动卡片 API 均不可用，仅支持单条文本回复。
-**Codex 报 `stream disconnected` / `error sending request`**：无法访问 `chatgpt.com`，请配置 `tools.codex.proxy` 或环境变量 `CODEX_PROXY`。
-**CodeBuddy 提示需要登录**：先执行 `codebuddy login`。`open-im` 不会从 `~/.open-im/config.json` 读取 CodeBuddy 的登录态。
-**WorkBuddy 无法连接**：重新运行 `open-im init` 登录。Token 可能过期——客户端会尝试自动重连，但如果 refresh token 失效，需要重新登录。
-**WorkBuddy 微信客服收不到消息**：确认在 `open-im init` 中完成了微信客服绑定。可重新运行 init 生成新的绑定链接。
+| 问题                     | 解决方案                                                         |
+| ------------------------ | ---------------------------------------------------------------- |
+| Telegram 无响应          | 检查网络，添加 `proxy` 或设置 `TELEGRAM_PROXY`                  |
+| QQ 无法连接              | 确认机器人已创建，检查 `QQ_BOT_APPID` / `QQ_BOT_SECRET`        |
+| QQ 重复回复              | 更新到最新版本                                                   |
+| 飞书卡片报错             | 未配置卡片回调时使用 `/mode ask` 或 `/mode yolo`                |
+| 企业微信收不到通知       | 先给机器人发一条消息                                             |
+| 钉钉无法回复             | 确认 Stream Mode 已启用，检查凭证配置                           |
+| 钉钉没有流式更新         | 自定义机器人仅支持纯文本；配置 `cardTemplateId` 启用流式卡片    |
+| Codex `stream disconnected` | 配置 `tools.codex.proxy` 或 `CODEX_PROXY`                    |
+| CodeBuddy 需要登录       | 先执行 `codebuddy login`                                        |
+| WorkBuddy 无法连接       | 运行 `open-im init` 重新登录，Token 可能已过期                  |
+| WorkBuddy 微信收不到消息 | 重新运行 `open-im init` 生成新的微信客服绑定链接                |
 ## License

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@wu529778790/open-im",
-  "version": "1.9.4-beta.11",
+  "version": "1.9.4-beta.12",
   "description": "Multi-platform IM bridge for AI CLI tools (Claude, Codex, CodeBuddy)",
   "type": "module",
   "main": "dist/index.js",
@@ -47,11 +47,11 @@
   "dependencies": {
     "@anthropic-ai/claude-agent-sdk": "^0.2.92",
     "@larksuiteoapi/node-sdk": "^1.59.0",
-    "centrifuge": "^5.3.0",
+    "centrifuge": "^5.5.3",
     "dingtalk-stream": "^2.1.4",
     "prompts": "^2.4.2",
     "telegraf": "^4.16.3",
-    "ws": "^8.18.0"
+    "ws": "^8.20.0"
   },
   "devDependencies": {
     "@eslint/js": "^9.15.0",
@@ -63,8 +63,8 @@
     "globals": "^15.12.0",
     "tsx": "^4.0.0",
     "typescript": "^5.0.0",
-    "typescript-eslint": "^8.15.0",
-    "vitest": "^4.1.0"
+    "typescript-eslint": "^8.58.0",
+    "vitest": "^4.1.2"
   },
   "engines": {
     "node": ">=20"