---
summary: "WeChat channel setup through the external openclaw-weixin plugin"
read_when:
  - You want to connect Klaw to WeChat or Weixin
  - You are installing or troubleshooting the openclaw-weixin channel plugin
  - You need to understand how external channel plugins run beside the Gateway
title: "WeChat"
---

Klaw connects to WeChat through Tencent's external
`@tencent-weixin/openclaw-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.
- `openclaw-weixin` is the Klaw channel id.
- `@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 Klaw core repo. Klaw provides the
generic channel plugin contract, and the external plugin provides the
WeChat-specific runtime:

1. `klaw 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. `klaw channels login --channel openclaw-weixin` starts QR login.
5. The plugin stores account credentials under the Klaw state directory.
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 Klaw agent, and sent back through the plugin outbound path.

That separation matters: Klaw 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:

```bash
npx -y @tencent-weixin/openclaw-weixin-cli install
```

Manual install:

```bash
klaw plugins install "@tencent-weixin/openclaw-weixin"
klaw config set plugins.entries.openclaw-weixin.enabled true
```

Restart the Gateway after install:

```bash
klaw gateway restart
```

## Login

Run QR login on the same machine that runs the Gateway:

```bash
klaw channels login --channel openclaw-weixin
```

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:

```bash
klaw config set session.dmScope per-account-channel-peer
```

## Access control

Direct messages use the normal Klaw pairing and allowlist model for channel
plugins.

Approve new senders:

```bash
klaw pairing list openclaw-weixin
klaw pairing approve openclaw-weixin <CODE>
```

For the full access-control model, see [Pairing](/channels/pairing).

## Compatibility

The plugin checks the host Klaw version at startup.

| Plugin line | Klaw version            | npm tag  |
| ----------- | ----------------------- | -------- |
| `2.x`       | `>=2026.3.22`           | `latest` |
| `1.x`       | `>=2026.1.0 <2026.3.22` | `legacy` |

If the plugin reports that your Klaw version is too old, either update
Klaw or install the legacy plugin line:

```bash
klaw plugins install @tencent-weixin/openclaw-weixin@legacy
```

## 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 Klaw'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 Klaw 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:

```bash
klaw plugins list
klaw channels status --probe
klaw --version
```

If the channel shows as installed but does not connect, confirm that the plugin is
enabled and restart:

```bash
klaw config set plugins.entries.openclaw-weixin.enabled true
klaw gateway restart
```

If the Gateway restarts repeatedly after enabling WeChat, update both Klaw and
the plugin:

```bash
npm view @tencent-weixin/openclaw-weixin version
klaw plugins install "@tencent-weixin/openclaw-weixin" --force
klaw gateway restart
```

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 Klaw needs. Update/reinstall after the plugin
publisher ships a fixed package, or temporarily disable/uninstall the plugin.

Temporary disable:

```bash
klaw config set plugins.entries.openclaw-weixin.enabled false
klaw gateway restart
```

## Related docs

- Channel overview: [Chat Channels](/channels)
- Pairing: [Pairing](/channels/pairing)
- Channel routing: [Channel Routing](/channels/channel-routing)
- Plugin architecture: [Plugin Architecture](/plugins/architecture)
- Channel plugin SDK: [Channel Plugin SDK](/plugins/sdk-channel-plugins)
- External package: [@tencent-weixin/openclaw-weixin](https://www.npmjs.com/package/@tencent-weixin/openclaw-weixin)