Skip to main content
OpenClaw connects to WeChat through Tencent’s external @tencent-weixin/openclaw-weixin channel plugin. Status: external plugin, maintained by the Tencent Weixin team. Direct chats and media are supported. Group chats are not advertised by the plugin capability metadata (it declares direct chats only).

​
Naming

  • WeChat is the user-facing name in these docs.
  • Weixin is the name used by Tencent’s package and by the plugin id.
  • openclaw-weixin is the OpenClaw channel id (weixin and wechat work as aliases).
  • @tencent-weixin/openclaw-weixin is the npm package.
Use openclaw-weixin in CLI commands and config paths.

​
How it works

The WeChat code does not live in the OpenClaw core repo. OpenClaw provides the generic channel plugin contract, and the external plugin provides the WeChat-specific runtime:
  1. openclaw plugins install installs @tencent-weixin/openclaw-weixin.
  2. The Gateway discovers the plugin manifest and loads the plugin entrypoint.
  3. The plugin registers channel id openclaw-weixin.
  4. openclaw channels login --channel openclaw-weixin starts QR login.
  5. The plugin stores account credentials under the OpenClaw state directory (~/.openclaw by default).
  6. When the Gateway starts, the plugin starts its Weixin monitor for each configured account.
  7. Inbound WeChat messages are normalized through the channel contract, routed to the selected OpenClaw agent, and sent back through the plugin outbound path.
That separation matters: OpenClaw core stays channel-agnostic. WeChat login, Tencent iLink API calls, media upload/download, context tokens, and account monitoring are owned by the external plugin.

​
Install

Quick install:
Manual install:
The plugin commands apply changes to a running Gateway. Check the application result; start the Gateway if it is offline.

​
Login

Run QR login on the same machine that runs the Gateway:
Scan the QR code with WeChat on your phone and confirm the login. The plugin saves the account token locally after a successful scan. To add another WeChat account, run the same login command again. For multiple accounts, isolate direct-message sessions by account, channel, and sender:

​
Access control

Version 2.4.8 does not register an OpenClaw pairing adapter or create pairing requests. The standard pairing list and approve commands cannot establish DM access for this version. QR login can still allow the user who scanned the code to chat with the bot. This version reads a legacy account allowlist JSON file instead of OpenClaw’s SQLite pairing store. When that list is empty, it falls back to the QR scanner’s saved user ID. If neither provides a user ID, its sender check admits any sender whose message reaches the plugin. On current OpenClaw, openclaw doctor --fix imports legacy approvals into SQLite and removes the source file. Previously approved secondary senders can therefore lose access in version 2.4.8. Revoking an approval in SQLite does not revoke access granted by the plugin’s legacy file or scanner fallback. Do not rely on standard pairing to manage or revoke DM access with version 2.4.8. If you need pairing enforcement, temporarily disable the plugin until a version with repaired pairing support is available. For integrations that implement OpenClaw’s pairing API, see Pairing.

​
Compatibility

The package declares these OpenClaw requirements: Version 2.4.8 declares >=2026.5.12, but its startup version guard still checks >=2026.3.22. Passing that guard alone does not satisfy the declared requirement. If the plugin reports that your OpenClaw version is too old, either update OpenClaw or install the legacy plugin line:
Plugin 2.4.6 imports the retired openclaw/plugin-sdk/channel-runtime path and cannot load on OpenClaw 2026.8.1. If startup reports that this subpath is not exported, update to plugin 2.4.8, which uses the available SDK path:

​
Sidecar process

The WeChat plugin can run helper work beside the Gateway while it monitors the Tencent iLink API. In issue #68451, that helper path exposed a bug in OpenClaw’s generic stale-Gateway cleanup: a child process could try to clean up the parent Gateway process, causing restart loops under process managers such as systemd. Current OpenClaw startup cleanup excludes the current process and its ancestors, so a channel helper cannot kill the Gateway that launched it. This fix is generic; it is not a WeChat-specific path in core.

​
Troubleshooting

Check install and status:
If the channel shows as installed but does not connect, enable it and inspect the running plugin:
If the Gateway restarts repeatedly after enabling WeChat, update both OpenClaw and the plugin:
If startup reports that the installed plugin package requires compiled runtime output for TypeScript entry, the npm package was published without the compiled JavaScript runtime files OpenClaw needs. Update/reinstall after the plugin publisher ships a fixed package, or temporarily disable/uninstall the plugin. Temporary disable: