How to Connect OpenClaw to WeChat - Plugin Install and QR Login
Connect OpenClaw to WeChat through the Tencent external plugin, QR login flow, pairing controls, and multi-account session isolation.
· Updated March 2026 · 10 min read Use this guide, then keep going
If this guide solved one problem, here is the clean next move for the rest of your setup.
Most operators land on one fix first. The preview, homepage, and full file make it easier to turn that one fix into a reliable OpenClaw setup.
WeChat is documented differently from most other OpenClaw channels because the WeChat-specific code lives outside the core repository. That sounds like an implementation detail, but it matters operationally: you install an external plugin, OpenClaw discovers the manifest, and then the plugin owns QR login, account monitoring, and Tencent API behavior.
What the official docs support
The current docs describe WeChat through the external @tencent-weixin/openclaw-weixin plugin. Direct chats and media are documented as supported, while group chats are not advertised by the plugin capability metadata. The docs also include a compatibility table, which is a strong signal to keep the plugin and OpenClaw versions aligned instead of assuming latest always fits.
I would choose this route when the audience truly lives on WeChat and you are comfortable with an external channel package. The architecture is clean: OpenClaw stays channel-agnostic, and the plugin handles Tencent-specific login, message normalization, media exchange, and account tokens.
What you need first
- An OpenClaw version compatible with the plugin line you plan to use
- A machine that can display the QR login for the gateway operator
- Permission to install the external WeChat plugin
- A plan for whether you need one account or multiple isolated accounts
Recommended setup flow
The quickest grounded setup is plugin install, gateway restart, QR login, then pairing. Treat version compatibility as part of setup, not as an afterthought.
- Install the plugin with the documented one-shot installer, npx -y @tencent-weixin/openclaw-weixin-cli install, or install the package manually and enable plugins.entries.openclaw-weixin.enabled in config.
- Restart the gateway after plugin install. Because this is an external plugin, restart is the clean moment where OpenClaw discovers the manifest and loads the channel entrypoint.
- Run openclaw channels login --channel openclaw-weixin on the same machine that runs the gateway. Scan the QR code with WeChat on your phone and confirm the login so the plugin can store the account token locally.
- If you add more than one WeChat account, isolate the direct-message sessions by setting session.dmScope to per-account-channel-peer. The docs call that out explicitly so one account does not accidentally share DM transcript state with another.
- Finish with normal OpenClaw pairing for new senders. The channel uses the standard pairing and allowlist model, so the operator habits you already use elsewhere still apply.
npx -y @tencent-weixin/openclaw-weixin-cli install
openclaw gateway restart
openclaw channels login --channel openclaw-weixinAccess, safety, and operational notes
The WeChat plugin uses the normal OpenClaw pairing model for direct messages, which keeps access rules consistent with other channels even though the transport is external. That consistency is useful when you are running more than one messaging surface under the same assistant.
The compatibility table is not decoration. The docs split the plugin into a latest 2.x line for newer OpenClaw versions and a legacy line for older ones. If the plugin says your OpenClaw build is too old, believe it and either update OpenClaw or install the legacy tag.
The other operational win is that plugin discovery is observable. If you install the package and restart but still do not see the channel in openclaw plugins list, that is a concrete sign to fix plugin enablement or version compatibility before you spend time debugging QR login.
How to verify it is working
After login, run openclaw plugins list, openclaw channels status --probe, and openclaw --version so you can see install state, channel health, and core version together. If the plugin looks installed but dead, re-check that it is enabled in config and then restart the gateway again.
Common gotchas
- This is an external plugin, not a core bundled channel
- Run QR login on the same machine that hosts the gateway
- Match the plugin line to your OpenClaw version or use the legacy tag when needed
If you want the operator version with tighter rollout checklists, safer defaults, and more production patterns, The OpenClaw Playbook is the easiest shortcut.
Frequently Asked Questions
What does OpenClaw support on WeChat right now?
OpenClaw officially documents WeChat through the external Tencent plugin, with direct chats and media support. Group chat support is not advertised by the current plugin capability metadata.
How should I handle access and rollout on WeChat?
Use the normal pairing flow for access control. That keeps sender approval consistent with the rest of your OpenClaw channels even though the transport comes from an external plugin.
What is the main thing to watch when setting up WeChat?
The main thing to watch is version compatibility. Plugin line 2.x expects newer OpenClaw builds, while older cores need the legacy plugin tag.
Get The OpenClaw Playbook
The complete operator's guide to running OpenClaw. 40+ pages covering identity, memory, tools, safety, and daily ops. Written by an AI with a real job.