How to Connect OpenClaw to Feishu (Lark)

Prerequisites

• ✓OpenClaw 2026.4.10 or above — run `openclaw --version` and upgrade with `openclaw update` if needed.
• ✓An existing OpenClaw gateway installation with the `openclaw` CLI available on your PATH.
• ✓A Feishu or Lark workspace where you can create and publish a bot in Feishu Open Platform / Lark Developer.
• ✓Permission in your Feishu/Lark tenant to grant the bot scopes and enable event subscriptions, including `im.message.receive_v1`.

Steps

1. 1

   Verify your OpenClaw version

   Feishu support requires a minimum OpenClaw version, so confirm this before you spend time wiring up bots. If you are on an older release, upgrade first so the Feishu channel and commands behave as documented.

   bashCopy

   openclaw --version
   openclaw update

2. 2

   Run the Feishu channel setup wizard

   Use the built-in channel login flow to create and connect a Feishu/Lark bot to your gateway. The wizard handles app creation and credentials; you authenticate by scanning a QR code from your mobile app.

   bashCopy

   openclaw channels login --channel feishu

3. 3

   Restart the OpenClaw gateway to apply Feishu settings

   After the wizard writes channel configuration, restart the gateway so it picks up the new Feishu account and connection mode. Skipping this restart is a common reason the bot appears connected in Feishu but never responds.

   bashCopy

   openclaw gateway restart

4. 4

   Configure direct message access control

   Decide who can DM your Feishu bot by setting the `dmPolicy` and, if needed, approving pairing codes. Pairing mode is useful when you want explicit approval for each new user instead of opening DMs to the whole tenant.

   bashCopy

   openclaw pairing list feishu
   openclaw pairing approve feishu <CODE>

5. 5

   Tune group chat behavior and mention requirements

   Control where the bot responds in group chats with `groupPolicy` and whether it needs an @mention. Start with an allowlist in busy tenants, then relax to open groups once you are confident the bot behaves well.

   jsonCopy

   {
     channels: {
       feishu: {
         groupPolicy: "allowlist",
         // Group IDs look like: oc_xxx
         groupAllowFrom: ["oc_xxx", "oc_yyy"],
       },
     },
   }

6. 6

   Restrict which users can trigger the bot inside a group

   For sensitive rooms, you can allow the bot in a group but restrict which senders it listens to. This is handy when you want a small operator set to control the agent while everyone else can read the replies.

   jsonCopy

   {
     channels: {
       feishu: {
         groupPolicy: "allowlist",
         groupAllowFrom: ["oc_xxx"],
         groups: {
           oc_xxx: {
             // User open_ids look like: ou_xxx
             allowFrom: ["ou_user1", "ou_user2"],
           },
         },
       },
     },
   }

7. 7

   Look up Feishu group and user IDs for routing

   You will need concrete `chat_id` and `open_id` values to build allowlists and bindings. Grab group IDs from the Feishu UI and user IDs from gateway logs or pairing requests so your config targets real entities.

   bashCopy

   openclaw logs --follow
   openclaw pairing list feishu

8. 8

   Enable streaming replies and quota optimizations

   Feishu supports streaming via interactive cards, which keeps long answers responsive. You can also disable typing indicators and sender name resolution to reduce API calls if you are close to quota limits.

   jsonCopy

   {
     channels: {
       feishu: {
         streaming: true, // enable streaming card output (default: true)
         blockStreaming: true, // enable block-level streaming (default: true)
       },
     },
   }
   {
     channels: {
       feishu: {
         typingIndicator: false,
         resolveSenderNames: false,
       },
     },
   }

9. 9

   Route Feishu conversations to specific agents

   Use bindings to send different Feishu DMs and groups to different OpenClaw agents. This lets you run, for example, a coding assistant for one user and a support bot in a specific group, all through the same gateway.

   jsonCopy

   {
     agents: {
       list: [
         { id: "main" },
         { id: "agent-a", workspace: "/home/user/agent-a" },
         { id: "agent-b", workspace: "/home/user/agent-b" },
       ],
     },
     bindings: [
       {
         agentId: "agent-a",
         match: {
           channel: "feishu",
           peer: { kind: "direct", id: "ou_xxx" },
         },
       },
       {
         agentId: "agent-b",
         match: {
           channel: "feishu",
           peer: { kind: "group", id: "oc_zzz" },
         },
       },
     ],
   }

Configuration

Troubleshooting

openclaw logs --follow

openclaw gateway status
openclaw logs --follow

openclaw gateway restart

Frequently asked questions