> ## Documentation Index
> Fetch the complete documentation index at: https://docs.avibe.bot/llms.txt
> Use this file to discover all available pages before exploring further.

# WeChat and Lark

> Use WeChat or Lark / Feishu for mobile-first and Asia-focused Avibe workflows.

# WeChat and Lark

Avibe also supports WeChat and Lark / Feishu, so the agent can live where your real work conversations already happen. Both connect out like the other platforms — no public inbound port for normal chat control — and the in-app setup wizard walks you through the platform-specific credentials.

<img src="https://mintcdn.com/cyhzhusunin/imJu-AQLssLHislx/assets/screenshots/en/platforms.png?fit=max&auto=format&n=imJu-AQLssLHislx&q=85&s=eb5d8c9d7f38ee5d71020f458c35ccc0" alt="Avibe platform connections for Slack, Discord, Telegram, WeChat, and Lark" width="1440" height="900" data-path="assets/screenshots/en/platforms.png" />

## WeChat

WeChat suits mobile-first personal workflows and China-native daily communication.

In the setup wizard, choose **WeChat** and follow the platform-specific prompts to connect your account, then select the chat where Avibe should respond. After it reports healthy, send a short smoke-test message in that chat.

## Lark / Feishu

Lark / Feishu suits teams already living in enterprise chat, approvals, and that collaboration ecosystem.

In the setup wizard, choose **Lark / Feishu**, configure the app credentials it asks for, and select the chats or channels where Avibe should respond. Lark connects over its WebSocket transport, so there are no inbound webhooks to expose.

> Setup specifics for WeChat and Lark are wizard-guided and evolve with each platform's own console. Follow the prompts in the wizard rather than a static field list, and use `vibe doctor` if a connection doesn't come up healthy.

## Outbound proxy

When the host running Avibe cannot reach WeChat or Lark / Feishu directly, set `proxy_url` on the matching platform config block from the Web UI. Both HTTP/HTTPS proxies and SOCKS proxies are supported (any `socks*://` scheme — `socks4`, `socks4a`, `socks5`, or `socks5h`). Saving the config block only persists the change; run `vibe restart --delay-seconds 60` afterwards so the new transport applies to live connections.

## Shared troubleshooting

| Symptom                             | Check                                                                           |
| ----------------------------------- | ------------------------------------------------------------------------------- |
| Messages do not arrive              | Platform credential, app installation, selected chat scope                      |
| Agent does not start                | Backend enabled, CLI path valid, working directory exists                       |
| Responses appear in the wrong place | Channel or chat routing settings                                                |
| WeChat / Lark unreachable from host | `proxy_url` on the matching config block; check firewall and TLS errors in logs |