Chat from WeChat. Approvals are not built.

Connect personal WeChat (微信) with a QR scan from the dashboard. Messages arrive over an outbound long-poll, so no public endpoint or tunnel is needed. For the work edition, use WeCom instead, which uses an official bot gateway.

What has been run on which harness is on the verification log; a feature without a dated row there is unverified.

Read this before you connect

This channel uses Tencent’s iLink bot API, which is not a published developer product. Its behaviour can change without notice, using a personal account as a bot may break WeChat’s terms, and accounts can be limited or banned. Prefer WeCom for anything that matters.

What works from WeChat today

• Chat in a direct message, with one reply per turn (a sent message cannot be edited, so the answer arrives when the turn completes) and Markdown preserved.
• Commands: /new, /compact, /stop and /help, with Chinese aliases (新对话, 清空, 停止, 帮助).

Set it up

1. Open Settings → Channels → WeChat in the dashboard and click Connect via QR.
2. Scan the code with the WeChat app and confirm on your phone.
3. Restart the gateway. The status reads Connected.

   warding restart

4. Allow yourself. The default policy is an allow-list with nobody on it, so a fresh bot ignores every message. DM the bot once, read your user ID from the gateway log, and add it to weixin.allowed_user_ids.

The credential is stored on the gateway side and never returned to the browser.

Who can reach it

Only the user IDs you allow-list; an empty list, or an unrecognised policy value, denies everyone. Group chats are not supported: the bot identity does not receive group events.

Limits, stated plainly

• Owner-only. One person runs this gateway, as themselves, with their files and credentials. There is no shared or team mode.
• One harness for chat. The docked harness answers every channel; switching is one setting. A spawned subagent can be routed to another installed harness; that is registered, not verified.
• Unofficial API, direct messages only, and one gateway per credential.
• Creating jobs from chat (and subagents, and questions the agent asks you mid-turn) relies on the agent’s own tools, which reach kiro-cli only today. On other harnesses, schedule from the dashboard or the CLI; see the schedule page.

Approvals: chat only · All ten channels · Full reference publication pending