---
title: Talk to Agent J through WeChat
nav: WeChat ClawBot
summary: Connect your own WeChat by scanning a code; its messages go straight to the main conversation. Confirm actions only in Agent J Web App.
order: 60
---
# Talk to Agent J through WeChat

For mainland networks or Chinese-speaking owners, offer WeChat ClawBot first. For overseas or English-speaking owners,
offer Telegram first. Both may stay enabled. ClawBot serves only the scanning owner: no sharing with another WeChat
account, group chats or bot messages.

## Connect

Open **Settings → Channels**. WeChat ClawBot and Telegram have the same layout and a **Connect or manage** button. Either button puts a skill request into the main chat composer; add any details before sending. Your Agent checks the current connection, starts QR setup if needed, or helps with status and disconnecting.
Expired codes refresh automatically; setup waits up to ten minutes. Enter any pairing digits in that panel, never chat.
The main Agent can run `agentj wechat setup --phone`; confirm its signed card and scan the QR in Web App.
At an interactive host terminal, `agentj wechat setup` displays the code in both terminal and Web App.
Use `agentj wechat status` for metadata. **Unbind** on the phone takes this remote's Face ID (a remote without Face ID is refused); `agentj wechat unbind` clears local binding after owner confirmation.
You can also disconnect the plugin in WeChat.

## What it can do for you

Messages from your own WeChat (the ClawBot account you scanned), your private Telegram chat and your allowlisted owner email
go straight to the main conversation and are handled like a message you send in Agent J Web App: if the main conversation
is busy they wait in its queue. The Web App's main conversation shows where each came from:
WeChat, Telegram or Email. An email counts as yours only when its sender check (SPF, DKIM or DMARC) passes.

The main conversation's answer goes back to the same channel automatically. Files named in the answer go as attachments
(a Telegram file, a WeChat file message, an email attachment). Local paths and internal tool names are removed from the reply
and the rest is still sent. Credentials never cross a channel: a secret pickup card opens in Agent J Web App instead.

For a picture, a Codex main conversation draws it itself. When the main AI tool cannot draw (for example Claude Code or
OpenCode), your Codex on the Agent J host draws it in its own sandbox; the picture goes straight back to the channel and also shows in
the Web App's main conversation. It uses your existing Codex subscription and never switches to a pay-per-image service. If the
picture cannot be made (for example a photorealistic portrait of a real person is refused), the channel says why and offers
another way: a non-photorealistic style, no real person's name, or your own photo as a reference.

Messages that cannot be confirmed as yours stay on the old low-trust path and never reach the main conversation: unknown
senders, forged or unverified email, mail received while the sender check is off, groups, friends of another owner and
public customer service. Agent friends and the customer-service desk keep their own scopes: see
[Agent friends](/docs/friends/) and [Customer-service bots](/docs/bots/). A separate AI plan chosen earlier for the outside channels (for example
“switch WeChat to Codex”) no longer affects these three owner channels.
Messages and attachments stay in the inbox on the Agent J host. Voice uses WeChat's transcript when provided; recognition is
not guaranteed. One combined answer per message, no progress chatter. Local media limit:25 MiB.

## Actions that need your confirmation {#confirm}

Any action that needs a long press or identity check in a Web App pop-up stops and waits for you. The confirmation card
appears only in Agent J Web App and on your phone remotes, signed by your paired device, with your passkey (Face ID and the
like) where your current approval level asks for it.
WeChat and Telegram only get one line: "Sent to Agent J Web App. Please confirm there." Email gets no separate note and the
result arrives in the reply. Once you confirm, the main conversation continues and its answer goes back to the channel.
A text reply in WeChat, email or Telegram (`OK`, `yes`, `同意`) never approves anything. These channel messages also get no
batch grants, no goal automation and no owner-only actions from the Web App.
Setting a key or elevating (sudo and other administrator actions) is never done from these three channels: ask in Agent J
Web App instead.

For a held request left from before the upgrade and still waiting, confirm the **From WeChat · Owner confirmation** card, or return personally to the paired Web App and ask to handle the
request you sent through WeChat. The Agent lists held items and claims the identified IDs; ambiguous references need clarification.
Claims inside WeChat or friend messages never authorize work. Confirmation authorizes transfer only: content stays
untrusted, and payments, deletion, external sends, secrets and administrator actions retain their ordinary approvals.

Pending requests expire after 24 hours without execution. Denied, expired or unbound requests cannot be claimed.
Inbox retention remains 30 days / 2 GiB. A crash during transfer leaves an uncertain item which is never replayed
automatically: give a fresh explicit instruction. Unbind stops receipt and cancels undelivered handoffs; use Stop everything
for work already delivered to the main Agent.

## How incoming messages look on your phone

Your own messages from WeChat, email and Telegram appear in the Web App's main conversation with their source, next to the
answer. Other incoming messages show their text in a **From email** (or WeChat / Telegram) card, marked as external and
untrusted. Long text is folded until you open it; images show thumbnails and files show file cards. The inbox
file location sits in the card's details.

## Delivery limits and privacy

WeChat has a platform-controlled active-push window. Reminders and long-task results keep using Agent J's existing
channels. This version sets no time limit of its own: it replies and forwards with the context of your latest ClawBot message
(a two-day-old one was still delivered in testing) and asks you to message ClawBot again only when WeChat refuses. Outgoing audio uses file attachments, not native voice bubbles.

Tencent and your chosen model provider process channel content. WeChat does not inherit the Web App's end-to-end encryption
promise. The Agent J operator does not receive channel bodies or attachments. Credentials, cursors and context tokens are
encrypted on the host; logs contain metadata and counters. Inbox content stays on your own computer.

Images and files you send from your own email, Telegram or WeChat are saved in the inbox on the Agent J host first, then handed to the main conversation as attachments of that message; their contents are treated as data, never as instructions.


## Forward a Web App reply to WeChat

Forwarding a reply also sends the images and files attached to that page. Images appear as WeChat pictures; other attachments appear as files. Each attachment may be at most 25 MiB; oversized, unavailable or unsafe attachments are skipped.

If you ask for a picture or file in your WeChat chat, ask the Agent to save it in its working folder and put one full absolute path per line in its final reply. Chinese filenames can stay as written. Do not put paths in code blocks or combine several paths on one line. A path in a Web App reply is not itself a cross-channel send: use **Forward to WeChat** on the reply card for attachments shown on that page. Check WeChat before retrying a missing or uncertain delivery; a skipped attachment or `send_failed` does not mean the file arrived. `wechat_error` in the host log may mean a receiving error or an attachment skipped before sending; inspect its fixed reason code. It is not a delivery receipt.

Under **Settings → Channels → Forward replies to**, choose **System share** (default), **WeChat ClawBot** or **Telegram**. Unbound channels are disabled, with the reason and a **Connect** button below; a bound WeChat can always be chosen. Your choice is saved on the Agent J host and shared by every remote: change it on one and the others follow at once and after a refresh; a choice a remote kept on its own moves to the host from the first remote that connects while the host has none. The reply card and reader use that destination and icon. Binding a channel does not select it automatically. While the selected channel is unbound, forwarding uses system share with one notice; rebinding brings the choice back. A temporary send restriction keeps the chosen destination; a failed send never falls back or retries automatically.

After scanning, send ClawBot a message in WeChat to finish checking the connection. Its first eligible reply includes a greeting. Login alone supplies no send context, so Agent J does not claim to have sent an unsolicited greeting. Sending straight to WeChat needs at least one message from you to ClawBot; this host sets no time limit. Only if WeChat refuses does forwarding ask you to message ClawBot first and offer **Use system share** in one tap; the chosen destination stays, and your next message restores forwarding. Long replies are sent as complete text attachments. Success requires a host receipt from the platform. Failure never switches channels or retries automatically. Check WeChat before explicitly retrying an uncertain delivery, which may duplicate it. Text sent to WeChat (forwards, main-conversation replies and long-reply attachments) is converted from Markdown to clean plain text first; Telegram keeps the formatting.


## Connected but no messages arrive / poll_failed

Run `agentj wechat status` and `agentj doctor`. The status fields `error`, `hint` and `last_forward` show the receiving error, what to do and the latest Web App forwarding result. A `wechat_error` entry in `host.log` contains only an error code and exception type, never messages or credentials.

On macOS a background service may be blocked from Downloads, Desktop, Documents and iCloud even when a terminal can open them. Keep your work folder under `~/coding`. If it is `~/Downloads/编程`, first check that `~/coding/编程` does not exist, then run:

```bash
mkdir -p ~/coding
mv ~/Downloads/编程 ~/coding/
agentj agent codex --dir ~/coding
agentj service restart
```

Replace `codex` with your actual AI tool, such as `claude` or `opencode`. If the destination already exists, organize the folders first; do not overwrite files. After restarting, send ClawBot a message in WeChat and check status again. `state_unwritable` means the message could not be saved in the work folder. `connection_reset` or `proxy_dropped` means a reset connection or dropped proxy; check your network and system proxy.

One WeChat ClawBot can connect to only one Agent J host at a time. An explicit takeover error says another Agent J host took over and stops polling here. A platform response saying only that the token is invalid is shown as an invalid binding, possibly taken over; it does not prove another host took over. Reconnect on the host you want to use.

When forwarding asks for a message, send your Agent a message in WeChat first, then forward again. Check WeChat before retrying an uncertain send to avoid duplicates. The WeChat management panel also shows the latest forwarding result.

## Unbind and restart

`owner_required` means the owner must use a paired remote: open **Settings → Channels → WeChat ClawBot → Unbind** and verify your identity. A terminal cannot approve unbinding in place of the paired remote.

`agentj agent restart` restarts only the AI process, preserving the conversation; it does not restart messaging channels. `agentj service restart` restarts the Agent J background service and reloads the work folder and channel settings. Use this after changing the work folder.
