Feishu Channel: Bot Overview, Features, and Configuration

The official @openclaw/feishu plugin is how OpenClaw reaches Feishu/Lark, the all-in-one collaboration platform. It covers bot DMs, group chats, streaming card replies, plus Feishu doc, wiki, drive, and Bitable tools.

Status: production-ready for bot DMs and group chats. Events travel over WebSocket by default, so no public URL is required; webhook mode remains optional.

In webhook mode, the Gateway HTTP port (usually 18789) is shared at /feishu/events. An existing installation keeps its previous endpoint when updates arrive, pinned explicitly via legacyWebhook; fresh installations open no extra port. Before relocating a callback that already exists, read the webhook migration guidance.

What each page covers

• Feishu setup: walk through the setup wizard and learn how durable inbound events work.
• Feishu access control: DM policy, group policy, mention gating, and looking up chat or user IDs.
• Feishu troubleshooting: bots that stay silent, events that never arrive, QR setup, and App Secrets that leak.
• Feishu advanced configuration: several accounts, limits, streaming, workspace tools, ACP sessions, and multi-agent routing.
• Feishu dynamic agents: isolate each user's agent, with a separate workspace per DM sender.
• Feishu configuration reference: all channels.feishu keys alongside their defaults.
• Feishu message types: the message types received and sent, stickers, and thread replies.

Where each section moved

Anchors for every section heading from the earlier single-page version are preserved on this page, so a link like /channels/feishu#streaming still resolves. Each entry below points to whichever page now carries that content.

• Quick start
• Inbound durability
• Access control
• Direct messages
• Group chats
• Group configuration examples
• Allow all groups, no @mention required
• Allow all groups, still require @mention
• Allow specific groups only
• Restrict senders within a group
• Bot-authored messages
• Get group/user IDs
• Get group/user IDs
• Group IDs (chat_id, format: oc_xxx)
• User IDs (open_id, format: ou_xxx)
• Troubleshooting
• Bot does not respond in group chats
• Bot does not receive messages
• QR setup does not react in the Feishu mobile app
• App Secret leaked
• Advanced configuration
• Multiple accounts
• Message limits
• Streaming
• Quota optimization
• Group session scope and topic threads
• Feishu workspace tools
• ACP sessions
• Persistent ACP binding
• Spawn ACP from chat
• Multi-agent routing
• Per-user agent isolation (Dynamic Agent Creation)
• Quick setup
• How it works
• Configuration options
• Session scope
• Typical multi-user deployment
• Verification
• Notes
• Configuration reference
• Supported message types
• Receive
• Send
• Sticker replies
• Sticker keyword search
• Threads and replies
• Run the channel setup wizard
• Verify the channel after setup
• Allow all groups, no @mention required
• Allow all groups, still require @mention
• Get group/user IDs
• Group IDs (chat_id, format: oc_xxx)
• User IDs (open_id, format: ou_xxx)
• Per-user agent isolation (Dynamic Agent Creation)

Common commands

Note

Native slash-command menus are not available in Feishu/Lark, so these commands have to be sent as plain text messages.

Because control commands skip both Feishu's message batching and the normal chat queue, you can inspect status or cut off a reply that is still running. Messages sent in ordinary chat are processed in sequence.

Related

• Channels Overview - every channel that is supported
• Pairing - how DM authentication and the pairing flow work
• Groups - mention gating and how group chats behave
• Channel routing - how messages are routed to sessions
• Reactions - what emoji reactions mean for the message tool
• Security - the access model and hardening