Message channel setup
Connect personal WeChat, WeCom or mainland-China Feishu to ClawPi to send tasks to this computer from external chats. Each platform supports multiple accounts. Connect an account, approve sender pairing, and authorize computer operation separately when needed.
Before starting
Install and sign in to the client, create an available workspace, and keep the computer running and online. Prepare the platform account or application management permission. Never send secrets to a chatbot.
Add an account
Open Message channels and select Add account on the intended platform card. Follow its guide until the account shows Connected. Credential fields are write-only and are not echoed after submission.
| Platform | Prepare | Instructions |
|---|---|---|
| Personal WeChat | Scan and confirm on your phone | Personal WeChat |
| WeCom | Intelligent bot Bot ID and Secret | WeCom |
| Feishu | Enterprise application App ID and App Secret | Feishu |
WeCom and Feishu receive events through outbound long connections without a public callback URL. Use an independent application for each Feishu connection account to avoid distributing messages across connections.
Pair senders and use a channel
- Send the bot a simple text task from the platform. Unknown senders receive a short pairing code.
- Return to Message channels → Pending pairings on the computer. Check the source identity and code. Requests remain valid for 15 minutes.
- Select the workspace this conversation may access and approve. Reject unfamiliar senders.
- Confirm the entry appears under Paired conversations and open its local conversation to review the task and result.
Approval processes the first message without resending. Rejected or expired requests do not send their content to the model. If no request appears, check connection, platform events and sender identity.
Direct chats pair both conversation and sender. Supported group messages must mention the bot and each member must pair separately. Approved members of one group share its conversation, so do not include materials meant for only one person. Messages in one conversation are ordered; different conversations may run concurrently.
Receive generated files
Explicitly request file creation and delivery from a paired conversation, then check for an actual attachment in the platform chat. See Files and attachments for formats, versions and delivery states. A local path is not proof of sending, and platform acceptance does not prove the recipient read it.
Authorize remote Windows control
Remote control is off by default. Enable Allow remote computer control for the paired conversation after reading the notice that screenshots are sent to the current model service. See Remote computer control for authorization, cancellation and limits.
Ordinary chat, a connected account and an approved pairing do not automatically authorize computer operation. External messages cannot upgrade channel conversations to full access.
Reconnect, move or delete
| Action | Effect |
|---|---|
| Stop, start or reconnect an account | Affects only that account |
| Change a conversation workspace | Subsequent tasks use a new conversation environment; original history remains local |
| Delete a pairing | Removes member approval and remote permissions, keeps history, and requires pairing on the next message |
| Delete an account | Stops connection and removes local credentials, pending message state and bindings; previous conversations remain local history |
Privacy and delivery
Account pages do not display Secrets, reply tokens or complete external identity identifiers. Pairing and workspace binding determine which tasks an external conversation can send to this computer. Check the contact before authorizing access.
Execution and platform delivery are separate stages. Inspect the local conversation, then message or attachment status. See Troubleshooting for failures.