Regional platforms
OmeniaClaw connects to WeChat through Tencent's external
@tencent-weixin/OmeniaClaw-weixin channel plugin.
Status: external plugin. Direct chats and media are supported. Group chats are not advertised by the current plugin capability metadata.
Naming
- WeChat is the user-facing name in these docs.
- Weixin is the name used by Tencent's package and by the plugin id.
OmeniaClaw-weixinis the OmeniaClaw channel id.@tencent-weixin/OmeniaClaw-weixinis the npm package.
Use OmeniaClaw-weixin in CLI commands and config paths.
How it works
The WeChat code does not live in the OmeniaClaw core repo. OmeniaClaw provides the generic channel plugin contract, and the external plugin provides the WeChat-specific runtime:
OmeniaClaw plugins installinstalls@tencent-weixin/OmeniaClaw-weixin.- The Gateway discovers the plugin manifest and loads the plugin entrypoint.
- The plugin registers channel id
OmeniaClaw-weixin. OmeniaClaw channels login --channel OmeniaClaw-weixinstarts QR login.- The plugin stores account credentials under the OmeniaClaw state directory.
- When the Gateway starts, the plugin starts its Weixin monitor for each configured account.
- Inbound WeChat messages are normalized through the channel contract, routed to the selected OmeniaClaw agent, and sent back through the plugin outbound path.
That separation matters: OmeniaClaw core should stay 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:
npx -y @tencent-weixin/OmeniaClaw-weixin-cli installManual install:
OmeniaClaw plugins install "@tencent-weixin/OmeniaClaw-weixin"OmeniaClaw config set plugins.entries.OmeniaClaw-weixin.enabled trueRestart the Gateway after install:
OmeniaClaw gateway restartLogin
Run QR login on the same machine that runs the Gateway:
OmeniaClaw channels login --channel OmeniaClaw-weixinScan 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:
OmeniaClaw config set session.dmScope per-account-channel-peerAccess control
Direct messages use the normal OmeniaClaw pairing and allowlist model for channel plugins.
Approve new senders:
OmeniaClaw pairing list OmeniaClaw-weixinOmeniaClaw pairing approve OmeniaClaw-weixin <CODE>For the full access-control model, see Pairing.
Compatibility
The plugin checks the host OmeniaClaw version at startup.
| Plugin line | OmeniaClaw version | npm tag |
|---|---|---|
2.x |
>=2026.3.22 |
latest |
1.x |
>=2026.1.0 <2026.3.22 |
legacy |
If the plugin reports that your OmeniaClaw version is too old, either update OmeniaClaw or install the legacy plugin line:
OmeniaClaw plugins install @tencent-weixin/OmeniaClaw-weixin@legacySidecar 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 OmeniaClaw'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 OmeniaClaw startup cleanup excludes the current process and its ancestors, so a channel helper must not kill the Gateway that launched it. This fix is generic; it is not a WeChat-specific path in core.
Troubleshooting
Check install and status:
OmeniaClaw plugins listOmeniaClaw channels status --probeOmeniaClaw --versionIf the channel shows as installed but does not connect, confirm that the plugin is enabled and restart:
OmeniaClaw config set plugins.entries.OmeniaClaw-weixin.enabled trueOmeniaClaw gateway restartIf the Gateway restarts repeatedly after enabling WeChat, update both OmeniaClaw and the plugin:
npm view @tencent-weixin/OmeniaClaw-weixin versionOmeniaClaw plugins install "@tencent-weixin/OmeniaClaw-weixin" --forceOmeniaClaw gateway restartIf 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 OmeniaClaw needs. Update/reinstall after the plugin
publisher ships a fixed package, or temporarily disable/uninstall the plugin.
Temporary disable:
OmeniaClaw config set plugins.entries.OmeniaClaw-weixin.enabled falseOmeniaClaw gateway restartRelated docs
- Channel overview: Chat Channels
- Pairing: Pairing
- Channel routing: Channel Routing
- Plugin architecture: Plugin Architecture
- Channel plugin SDK: Channel Plugin SDK
- External package: @tencent-weixin/OmeniaClaw-weixin