Regional platforms
Feishu setup
Run the channel setup wizard, then understand how OpenClaw durably accepts inbound Feishu events.
Quick start
Run the channel setup wizard
openclaw channels login --channel feishuThis installs the @openclaw/feishu plugin if it is missing, then walks through setup:
- Manual setup: paste an App ID and App Secret from Feishu Open Platform (
https://open.feishu.cn) or Lark Developer (https://open.larksuite.com). - QR setup: scan a QR code in the Feishu app to create a bot automatically. This flow locks DMs to your own account (
dmPolicy: "allowlist"with youropen_id).
The wizard also asks for the API domain (Feishu vs Lark) and the group policy. If the domestic Feishu mobile app does not react to the QR code, rerun setup and choose manual setup.
After setup completes, restart the gateway to apply the changes
openclaw gateway restartInbound durability
OpenClaw durably queues authenticated im.message.receive_v1 and drive.notice.comment_add_v1 envelopes before agent dispatch. In webhook mode, the durable 200 carries x-openclaw-delivery-accepted: durable; verification challenges, non-durable event types, and error responses omit the marker, so reverse proxies can require it to distinguish durable acceptance from a generic 200. Pending or retryable events survive a Gateway restart, remain serialized per chat or document, and use Feishu's event ID to suppress duplicate queue entries while the active or retained completion record exists.
If a WebSocket event cannot be persisted after bounded retries, OpenClaw closes that socket and forces a fresh authenticated connection instead of continuing past an uncommitted turn. Other Feishu event types, including reactions and VC meeting invitations, use their normal event paths and do not receive this durable-queue guarantee.
