Connect WeChat: QR login, permissions, and private chats
Scan to connect personal WeChat, configure project access, verify private replies, and handle recovery.
ChannelsWhat the WeChat channel does#
Connect a personal WeChat account by scanning a QR code, then send tasks to a project assistant and receive replies in private chat. The current iLink integration supports a single bot and direct messages; WeChat groups are not supported.
Before you start#
Have a WeChat account available for scanning, a demo project, and a provider/model that already works in Onevium. Keep the computer and Onevium running with network access.
Scanning supplies the login credentials; you do not enter a WeChat App ID or API key. Confirmation completes login, but you still need to save the bot configuration. Enter any verification code only in the dedicated login field, not an ordinary conversation.
Scan and create your first connection#
- Open Channels → New Channel. Choose Bot as the creation type and WeChat as the platform.
- Select Generate QR code, scan with the intended WeChat account, and confirm on the phone. If requested, enter the digits shown in WeChat in the verification field and verify.
- After “WeChat connected,” select Continue setup. Generate a new code if the QR or login ticket expires, then finish saving.
- Fill in the following configuration and select Create Bot. The app attempts to start the connection after creation; inspect its final state, not just QR confirmation.
| Field | First setup |
|---|---|
| Bot Name | A recognizable name such as “WeChat project assistant” |
| Model | A provider and model already verified to work |
| Working Directory | A demo project without sensitive material |
| Conversation Mode | Keep separate conversations per person |
| Auto-approve Actions | Keep the default approval setting initially; tool rules still apply |
| Chat Scope | Fixed to DMs only for WeChat |
| Direct Message Policy | Keep the allowlist; the scanning account is added automatically |
| System Prompt | Define the role, such as answering project documentation questions without editing files |
If credentials are already used by another bot, open that existing connection rather than duplicating it. Reconnecting an existing bot cannot switch it to a different WeChat account; create a new bot for another account.
Who can send messages and approve actions#
The default allowlist includes the scanning account. Additional entries use platform user IDs, one per line, not nicknames. Do not open access to everyone merely to troubleshoot.
WeChat approvals use text prompts. Inspect the tool, input, and target, then reply allow/deny or 允许/拒绝 in that same private conversation. These are not DingTalk-style card buttons, and the words do not grant global permission when no approval is pending.
Tool approval, DM admission, and conversation mode are separate controls. Shared-conversation settings do not enable WeChat group support.
Verify two private messages#
Open the private conversation associated with the QR connection in WeChat and send:
The code for this test is wechat-demo-1.
Reply only with that code. Do not perform other actions.
After the reply, ask “What was the test code?” Confirm that:
- The correct WeChat connection in Onevium shows the private conversation and messages.
- Both replies reach the intended account and the second uses this conversation's context.
- If a tool approval appears, work actually continues after it is resolved; a text reply does not prove a file operation succeeded.
This connection does not provide contact nicknames. In the connection's chat settings, select the private chat, enter a Local name, and save. It changes the Onevium display only, not the WeChat nickname.
Message and recovery boundaries#
| Content or situation | Current behavior |
|---|---|
| Text, images, files | Supported in both directions; start with a small attachment, with a 20 MiB per-file limit |
| Voice with transcript text | Uses text supplied by the platform; not automatic recognition of every voice message |
| Voice without text, video | Unsupported; send text, an image, or a file instead |
| Long replies | May arrive as several text messages; no Feishu/DingTalk-style streaming cards |
| Proactive sending | Requires an established reply context for that private chat; send a fresh WeChat message when prompted |
| Ordinary network interruption | Automatic retries with saved received messages and cursor recovery |
| Expired login or failed local persistence | Requires attention; rescanning is not a fix for every failure |
Inspect existing messages and execution state after recovery instead of resending the same task repeatedly. A stopped connection or offline computer cannot be assumed to receive and execute continuously. Local recovery records are not a cross-system exactly-once guarantee.
Common problems#
| Symptom | First checks |
|---|---|
| WeChat platform missing | Check the applicable version at the top of this page and select Bot as the creation type |
| Still waiting after scanning | Phone confirmation, verification code, or expired QR |
| Account mismatch or credentials in use | A different scanned account or an existing bot for the connection |
| Connected without replies | Saved/running state, private-chat scope, sender allowlist, and working model |
| Repeated reconnect messages | Network and login state; when login is required, use Reconnect WeChat and save |
| Asked to send a new message | Send one from the same WeChat private chat to establish reply context |
| Unable to save or restore messages | Inspect local storage and retain the error; do not first delete the bot or database |
Next steps#
Compare channels in the overview, choose an action scope with permissions, and diagnose model connections through providers. Verify text first, then the attachments or project tools you need.