Feishu

OpenClaw connects to Feishu/Lark (the all-in-one collaboration platform) through the official @openclaw/feishu plugin: bot DMs, group chats, streaming card replies, and Feishu doc/wiki/drive/Bitable tools.

Status: production-ready for bot DMs + group chats. WebSocket is the default event transport (no public URL needed); webhook mode is optional.

Webhook mode shares the Gateway HTTP port (normally 18789) at /feishu/events. Updates preserve an existing installation's previous endpoint with an explicit legacyWebhook pin; new installations open no separate port. See the webhook migration guidance before moving an existing callback.

What each page covers

• Feishu setup — run the setup wizard and understand durable inbound events.
• Feishu access control — DM policy, group policy, mention gating, and chat/user ID lookup.
• Feishu troubleshooting — silent bots, missing events, QR setup, and leaked App Secrets.
• Feishu advanced configuration — multiple accounts, limits, streaming, workspace tools, ACP sessions, and multi-agent routing.
• Feishu dynamic agents — per-user agent isolation with its own workspace per DM sender.
• Feishu configuration reference — every channels.feishu key with its default.
• Feishu message types — received and sent message types, stickers, and thread replies.

Where each section moved

Every section heading from the previous single-page version keeps its anchor here, so an existing link such as /channels/feishu#streaming still resolves. Each entry points at the page that now holds the 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

Control commands bypass Feishu's message batching and ordinary chat queue, so you can check status or interrupt a running reply. Ordinary chat messages are handled in order.

When work is active, /followup <message> reports queue acceptance without waiting for that work to finish, including when another followup is already waiting. Each followup keeps the submitting sender's identity and leaves the conversation's queue mode unchanged. The durable ingress claim remains held for recovery until the queued turn is adopted; it does not block later inputs from reaching admission. Ordinary buffered messages retain their chat ordering.

Related

• Channels Overview - all supported channels
• Pairing - DM authentication and pairing flow
• Groups - group chat behavior and mention gating
• Channel routing - session routing for messages
• Reactions - emoji reaction semantics for the message tool
• Security - access model and hardening