WeChat (Weixin)

Connect Crew to personal WeChat (微信) through Tencent's iLink bot API. Sign-in is a QR scan from the dashboard; messages arrive over HTTP long-poll, so no public endpoint, webhook, or tunnel is required.

• Unofficial surface. The iLink bot API is not a published Tencent developer product. Behavior can change without notice, and using a personal account as a bot may violate WeChat's terms of service. Accounts can be limited or banned.
• DM only. The iLink bot identity generally does not receive group events. Group chat is unsupported.
• One poller per credential. Only a single gateway may long-poll a given bot credential at a time.

Prefer WeCom for anything business-critical.

1. Open Settings → Channels → WeChat in the dashboard
2. Click Connect via QR
3. Scan the code with the WeChat mobile app and confirm on your phone
4. Restart the gateway — the status pill turns Connected

The bot credential is written server-side (into the credential store, never returned to the browser). Only the non-secret account ID and connection status are exposed to the dashboard.

The QR flow requires the dashboard UI — there's no CLI-only path for the initial sign-in. After connecting via the dashboard, manage settings in config.json:

{
  "weixin": {
    "enabled": true,
    "dm_policy": "allowlist",
    "allowed_user_ids": ["user-id-from-log"]
  }
}

Then: kirocrew restart

Who can message the bot maps to weixin.dm_policy:

The default is allowlist with an empty list, which authorizes nobody — a freshly connected bot ignores every DM until you add an ID. To collect a user ID, have the person DM the bot once and read the ID from the gateway log.

Context is managed automatically: at soft_threshold_pct (80%) the bot suggests /compact or /new; at hard_threshold_pct (95%) it compacts on its own.

• One reply per turn — iLink cannot edit a sent message, so the answer is buffered and delivered when the turn completes (not streamed). The native "typing…" indicator runs for the duration.
• Markdown is preserved — iLink clients render it. Replies longer than 4000 characters split at paragraph/code-fence boundaries.
• Tool calls and reasoning are not echoed to the chat (they would each become a separate bubble).
• No approval buttons — iLink has no interactive controls. In interactive mode, tools needing approval are denied by default. Use auto or trust mode, or approve from the dashboard.
• Text only — media (images, voice, files) is not supported yet.

Set under weixin in config.json (or via the Settings panel):

The credential is read from the WEIXIN_TOKEN credential (env / .env / credential store).