Connect Feishu

This connection supports enterprise-created applications on mainland-China Feishu, not international Lark. You need permission to create and publish an application, a workspace and an online ClawPi client.

Create an application and enable its bot

Open the Feishu developer console, create an enterprise application, set its name and description, and add bot capability. Find its App ID and App Secret under credentials and basic information.

Use a separate application for each independent ClawPi connection account. Connecting the same application to several running clients can distribute events to other connections.

Configure events and permissions

Follow the console's event subscription instructions, choose long-connection delivery and add the receive-message event im.message.receive_v1. This is an event name, not a permission name; searching for it in permissions does not create a subscription.

Required operation	Platform capability to verify
Receive direct bot messages	Receive direct messages sent to the bot
Receive group instructions	Receive group messages mentioning the bot
Reply	Send messages as the application
Receive and send images or files	Relevant message-resource read and upload permissions

Request only the permissions needed and complete administrator approval. Check Feishu's send-message documentation for reply permissions. ClawPi uses outbound long connections without a public callback URL.

Connect from ClawPi

1. Open Message channels → Feishu → Add account.
2. Enter the same application's App ID as appId and App Secret as appSecret, then submit. Secrets are not echoed.
3. If Feishu cannot detect a connection while saving its long-connection configuration, keep the client running and return to the platform to save.
4. Create and publish an application version. Verify bot capability, events and permissions are effective and include your test member in the availability range.
5. Check Connected in ClawPi, send text directly to the bot from Feishu, and approve pairing on the computer.

Success means the task appears in the intended workspace and the result returns to the source Feishu conversation. Connection status alone does not prove application publication, permissions or pairing.

Diagnose missing replies

Symptom	Check in order
Bot cannot be found	Bot capability, publication and member availability
Connected but no pairing request	Receive-message event, direct/group permissions and bot mention
Computer executed but Feishu has no reply	Send-message permission, resource permissions and client errors
Intermittent replies	Whether multiple computers share the App ID

Every group sender must pair individually. Continue with Connect and pair, and use Files and attachments for file delivery.