How to Connect OpenClaw to Feishu - QR Setup and Group Controls

Feishu and Lark are good examples of a channel where the official docs optimize for operator speed. Instead of walking through a long manual app registration guide, OpenClaw documents a QR-based channel login flow that creates the bot for you, then lets you tighten DM and group behavior in config.

What the official docs support

The docs mark Feishu or Lark as production-ready for bot DMs and group chats, with WebSocket as the default transport and webhook mode optional. They also note a version requirement: this documented flow requires OpenClaw 2026.4.24 or above, so checking openclaw --version is not just busywork here.

This setup is a strong choice for internal teams that already collaborate in Feishu or Lark and want an assistant that stays in the same chat fabric. Group policies, mention requirements, and per-group sender allowlists make it practical to start conservative and open things up later only where the bot is genuinely useful.

What you need first

• OpenClaw 2026.4.24 or above
• A phone with the Feishu or Lark app for QR login
• Access to the gateway shell so you can run login and restart commands
• A plan for which groups and users should be allowed

Recommended setup flow

The shortest grounded setup is to let OpenClaw do the login work, then use config only for access policy and group behavior.

1. Run openclaw channels login --channel feishu and scan the QR code with your mobile app. The docs describe this as the main setup flow, and it is the fastest way to get a functioning bot account without hand-editing secrets first.
2. Restart the gateway after the login flow finishes. That restart matters because it loads the new channel state and makes the bot ready to receive direct messages and group messages.
3. Choose the DM policy that matches your risk tolerance. Pairing is the safe default, allowlist limits access to specific users, open allows everyone, and disabled shuts DMs off completely. If you use pairing, approve requests with openclaw pairing list feishu and openclaw pairing approve feishu <CODE>.
4. Decide how groups should behave before you drop the bot into busy chats. The docs show groupPolicy open, allowlist, or disabled, with requireMention true by default. You can also restrict a single chat to specific open_id values under channels.feishu.groups.<chat_id>.allowFrom.
5. Fetch the IDs you need. Feishu group IDs live in the group settings page, and user open_id values can be discovered by sending a DM and watching openclaw logs --follow or by checking pending pairing requests.

openclaw channels login --channel feishu
openclaw gateway restart

Access, safety, and operational notes

Feishu is nice because its access model is straightforward. DMs and groups are controlled separately, mention gating is explicit, and the docs show stable IDs for both chats and users. That means you can keep the bot from becoming noisy without inventing a lot of custom rules.

The docs also call out a practical detail that trips teams up: Feishu does not provide native slash-command menus in this integration, so commands like /status, /reset, and /model are sent as plain text messages rather than picked from a platform command UI.

How to verify it is working

Test the bot in a DM first, then in one controlled group. If the group stays silent, check the obvious items in order: the bot was added to the group, groupPolicy is not disabled, the message includes an @ mention if requireMention is still true, and the gateway logs show inbound events arriving.

Common gotchas

• This documented flow requires OpenClaw 2026.4.24 or above
• Feishu group replies require an @ mention by default
• User and group IDs are stable and worth collecting early for allowlists

If you want the operator version with tighter rollout checklists, safer defaults, and more production patterns, The OpenClaw Playbook is the easiest shortcut.