Weixin (WeChat)

Connect Weixin by scanning a login QR code from the Gateway console. The login credentials are stored on the Gateway host, so perform setup on the xopc instance that will stay running.

Connect

1. Open Channels → Weixin.
2. Choose Login or Configure.
3. Scan the QR code with the intended Weixin account.
4. Confirm the login in Weixin if prompted.
5. Keep the direct-message policy set to Pairing.
6. Save optional account and streaming settings.

After login, send a test message and approve the pairing request in xopc.

Access policy

Pairing is recommended because an unknown sender must present a one-time code before messages reach the Agent. You can also approve on the Gateway host:

xopc channels pairing approve weixin <code> --account default

Use Allowlist for fixed users, Open only for an intentionally public assistant, and Disabled to block direct messages.

Multiple accounts

Add account-specific settings only when you need separate Weixin identities or routing. Complete and verify one account first; use clear account names so pairing and logs are easy to interpret.

Troubleshooting

• QR code expired: close the dialog and start a new login.
• Login succeeds but messages do not arrive: confirm the same Gateway holds the saved credentials and remains running.
• Unknown user gets no code: check that direct-message policy is Pairing rather than Allowlist.
• Reply fails: verify local Chat and inspect the Weixin channel logs.

Do not copy the stored login files to an untrusted machine. Re-login if credentials are revoked or moved to a new Gateway host.

Configure capabilities in conversation

A paired, explicitly approved private chat can request Skill installation and use. HTTP MCP requests return a secure page where the Gateway owner signs in, checks the exact service and Weixin identity, and approves the connection before Token entry or OAuth. The original Weixin chat continues automatically; failed result delivery can resend the saved result without repeating the read.

Secure MCP return requires a phone-accessible HTTPS gateway.publicUrl, session.dmScope=per-account-channel-peer, and no identity merging. Shared chats and group configuration are outside this scope. Connections join shared Gateway capabilities under the assistant's tool policies; pairing does not grant general administration rights.

Self-contained reminders use the original account and peer through the durable automation delivery outbox. See the implementation and acceptance record for exact scope; local protocol acceptance does not imply official WeChat or physical-phone acceptance.