OpenClaw Feishu configuration reference

The Feishu configuration reference is a single table, but it is where the defaults that shape every other Feishu page live: streaming on, mentions required unless the group policy is open, reply references on every message, permission tools off. Here is the table read in groups, and the one validation rule at the bottom that stops a gateway from starting.

Transport and accounts

• The channel is enabled by default, the domain selects the API host with feishu as default, lark as the alternative or a full base URL, the connection mode is websocket by default with webhook as the alternative, and the default account names the account used when outbound APIs give no account ID.
• Webhook mode needs a verification token and an encrypt key, with the webhook path defaulting to the feishu events route, the bind host to loopback and the bind port to 3000.
• Each account under the accounts map carries its app ID and app secret, an optional domain override, a reply mode that inherits from the channel, a TTS override that defaults to the global TTS block, and a sticker action override that inherits.
• The DM policy is pairing by default with allowlist and open as the others, and the DM allowlist holds open IDs; the group policy is allowlist by default with open and disabled, the group allowlist admits groups, the group sender allowlist applies one sender list to all groups, the mention requirement is true except false under an open policy, and the allow-bots flag, off by default, accepts other bots that mention this bot under bot loop protection.

If an existing configuration contains a noncanonical path, run openclaw doctor --fix to repair it before starting the gateway.

Groups, sessions, delivery

Per-group entries under the groups map take a mention override, which also admits the group in allowlist mode, an enabled flag that is true by default, and a per-group sender allowlist that overrides the global one. The group session scope defaults to group with group-sender, group-topic and group-topic-sender as alternatives, the reply mode defaults to all with off, first and batched available, reply-in-thread is disabled by default, and reaction notifications default to own with off and all. The sticker action is off by default, sticker sets have no default, meeting auto-join is off, and the dynamic-agent block carries the enabled flag, the workspace and agent directory templates and the unlimited maximum. Delivery keys are the 4000-character text chunk limit, the length chunk mode with newline as the alternative, the 30 MB media cap, the automatic render mode with raw and card as alternatives, streaming card output in partial mode by default with off as the alternative, completed-block streaming off, the typing indicator and sender name resolution both on, and config writes on because dynamic agents need them.

Tools and the webhook path

• The tool gates enable the document, chat info, knowledge base, cloud storage, scope diagnostic and Bitable tools by default, with the knowledge base tool requiring the document tool, and the permission management tools off by default; per-account Bitable gates inherit.
• In webhook mode both the channel and the per-account webhook paths must be canonical HTTP request paths beginning with a slash, such as the default events route, an optional query string must match exactly, and full URLs, relative paths, URL fragments, dot segments and unencoded spaces or Unicode are rejected.
• A configuration that already holds a non-canonical path is repaired by the doctor fix before the gateway starts.

OpenClaw on Feishu is the channel post these keys belong to, and OpenClaw Feishu advanced configuration the page that explains the streaming, session and tool keys in depth.

Defaults that decide behaviour

Three defaults in this table explain most first-week surprises: streaming cards are on, so replies arrive as cards that update; reply references are on for every message; and permission tools are off, so an agent cannot change document sharing until someone opens that gate. OpenClaw Feishu setup shows the wizard that writes the first few keys, and OpenClaw Microsoft Teams configuration the equivalent key list for Microsoft Teams.

On Diali

Feishu and Lark are not among the channels Diali connects today: WhatsApp, Telegram, Discord, Slack, Mattermost, Matrix, SMS and voice. Hosted OpenClaw on Diali is the assistant and Diali security describes the boundary that applies to each connected channel.

• WebSocket by default; webhooks need a token, a key and a canonical path.
• Streaming cards on, replies referenced on all, permission tools off.
• Webhook paths start with a slash and nothing else.