openclaw-wechat plugin
WeCom channel for OpenClaw: the agent replies in corporate WeChat, and personal WeChat connects through the same app
- 152 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- A public address accepts messages from WeCom users, and the Secret and encryption key sit in the OpenClaw configuration.
- The agent answers on behalf of a company app and can send files and images to the chat.
Install
- Works in
Manual install
openclaw plugin install --path /path/to/openclaw-wechatClone the repository and run `npm install` first, then point the command at the folder. Manual registration in `~/.openclaw/openclaw.json` is also possible.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- A public address accepts messages from WeCom users, and the Secret and encryption key sit in the OpenClaw configuration.
- The agent answers on behalf of a company app and can send files and images to the chat.
This is third-party code. Review the repository files before installing.
What it does
openclaw-wechat is a channel plugin for OpenClaw. Through a custom WeCom (corporate WeChat) app the agent receives messages and replies to people. Personal WeChat works through the same app: in the WeCom admin console, under My Enterprise, WeChat Plugin, an account is linked by QR code, and a person writes to the agent from the ordinary messenger. The plugin receives text, images, voice, video, files and links, and sends text, images, video and files. Voice becomes text through built-in WeCom recognition, a remote Qwen3-ASR server or a local FunASR, falling back automatically. The agent remembers the last 20 messages of a chat, and the commands `/help`, `/status` and `/clear` manage the session. Long replies are split at 2048 bytes, and Markdown is converted to plain text because WeCom does not render it. The repository also holds a `wecom-notify` skill: the `send_wecom.py` script sends WeCom a text, an image or a file, for example a notice that a long task has finished.
Who it is for. WeCom administrators and OpenClaw developers who need an agent chat channel in corporate and personal WeChat.
Good fit when
- Employees message the OpenClaw agent in WeCom and get answers in the same chat.
- A client or colleague writes from personal WeChat, and the agent answers through the linked WeCom app.
- Voice messages in the chat become text before the agent replies.
- After a long task the agent sends a summary, a chart image or a report file to WeCom through the `wecom-notify` skill.
- One OpenClaw serves several WeCom apps, with each one configured through the `WECOM_<ACCOUNT>_*` scheme.
Not a fit when
- The agent must be connected to another messenger: OpenClaw has its own channels for Telegram and Discord.
- No WeCom administrator is available, and without one an app cannot be created or personal WeChat linked.
- The server has no public callback address and no stable outgoing IP, so WeCom will not accept the requests.
- The agent must send voice messages: the plugin only receives voice.
Example request
When the build finishes, send me a chart image and a short summary in WeCom.Limitations
The last commit dates from March 2026. The plugin targets OpenClaw, and version 0.3.7 is compatible with OpenClaw 2026.3 and newer. It needs WeCom administrator rights, a public callback address (Cloudflare Tunnel is recommended) and the server outgoing IP on the app trusted IP list, otherwise the API returns error 60020. AgentId, Secret, Token and EncodingAESKey belong to one app: when mixed, the agent sends messages but receives no replies. The `wecom-notify` skill carries the author settings, the default recipient and the address of their proxy, so replace them with your own.
How to disable. Remove the `wecom` plugin from the `plugins` block in `~/.openclaw/openclaw.json`, delete the `WECOM_*` variables and stop the tunnel. The app itself can be switched off in the WeCom admin console.
FAQ
Can people write to the agent from personal WeChat?
Yes. The WeCom app is linked to personal WeChat by QR code in the admin console, under My Enterprise, WeChat Plugin. After that, messages go through the same app.
How do I check that the channel works?
Run `openclaw channels status --probe`: the channel should report the running state. The `/wecom/callback` address answers with `wecom webhook ok`, and an incoming message leaves a `wecom inbound:` entry in the logs.
Why does the agent send messages but get no replies?
Most likely AgentId and Secret come from one app while Token and EncodingAESKey come from another. Take all four values from the settings of a single WeCom app.
What does error 60020 mean?
WeCom rejects requests from an IP missing in the trusted list. Add the outgoing address of the server to the Trusted IP list of this app: every app has its own list.
How do I connect several WeCom apps?
Extra accounts are set with variables of the form `WECOM_<ACCOUNT>_*`, for example `WECOM_SALES_CORP_ID`, next to the variables of the default account.
Discussion
No questions or reviews yet.
Related
PluginsAn MCP channel that passes WeChat messages into a Claude Code session and sends the agent's replies back to the same chat
A CLI that passes your WeChat messages to an agent through the official ClawBot (iLink) and sends replies back
MAX plugin for OpenClaw
openclaw-max-plus
A channel plugin that connects the OpenClaw AI assistant to the MAX messenger via the official Bot API: text, media, buttons, streaming, multiple accounts
WeChat Automation API
wechat-automation-api
A skill for agents on Windows that sends text, images and files through an already running desktop WeChat, with an HTTP API and a queue as well
MAX plugin for OpenClaw
openclaw-max
A channel plugin that connects the OpenClaw AI assistant to the MAX messenger: text, attachments, buttons, pinning and webhooks
Connects Claude Code, Cursor, Codex or OpenCode to Telegram, Slack and Discord: teammates message a bot, an agent replies
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| openclaw-wechat (this card) | no | 152 | ||
| WeCom CLI | yes | 3,305 | the official WeCom CLI with skills for messages, documents and calendar; this one is the channel through which an OpenClaw agent answers people | |
| Claude Code WeChat Channel | no | OAuth | 311 | passes WeChat messages into a Claude Code session; this one is a channel for an OpenClaw agent through a WeCom app |
README in short
The repository is a fork of the OpenClaw-Wechat plugin at version 0.1.0 with video, files, links, several accounts and chat memory. Version 0.3.7 fixes behavior on OpenClaw 2026.3 and newer. Setup takes six steps: the WeCom app, company data, message receiving, variables, public access and trusted IPs.