Feishu Bot access

Each Bot is bound to a Multica agent one-to-one. Binding another agent creates another bot; an agent can never have two bots.

Entrance	Behavior
Agent → Integrations	The agent details page has an Integrations tab (there is also a corresponding block in the left column). Owners and administrators can see Binded to Feishu here; after binding, it will become the Connected to Feishu logo with a Manage in Feishu link.
Private Chat Bot	Workspace members send messages directly to the Bot in Feishu. Each conversation becomes a Multica chat session for the agent, and the agent replies in the session.
@it in the group	Add the Bot to Feishu Group and then @it. Bot only reads @ its message and does not monitor the entire group.
/issue Command	Entering /issue <title> (you can attach text) will create a new Multica issue in the workspace and record it in your name.
Real-time reply card	The Bot will issue an interactive card that will be continuously updated as the agent runs - progress, final reply, or error report.

1. Open the agent in Agents → Your Agent.
2. Enter the Integrations tab (or use the Integrations block on the left column) and click Bind to Feishu.
3. A QR code pops up. Use your phone to open Feishu → Scan and authorize this new PersonalAgent Bot.
4. After scanning the QR code, the pop-up window closes and the agent displays Connected to Feishu. Your own Feishu identity will be automatically bound to your Multica account. Once bound, you can start talking to the Bot.

QR codes are one-time use and will expire after a short period of time. If it expires before authorization, click Re-scan the code to get a new code.

After the agent is connected, the Bind to Feishu button will be replaced by the Manage in Feishu link. When you need to adjust the permission scope, change the name, or apply for more permissions, use it to open the Bot's application page in Feishu - re-scanning is deliberately disabled to avoid orphaning existing Bots.

The first time you send a message to the Bot, it will reply with a card allowing you to bind your Feishu identity. Click the link, log in to Multica, and your Feishu account will be associated with your Multica membership. It is this step that allows the agent to act as you - for example /issue will put the issue in your name.

Only workspace members can use the bot. If you are not a member, or have skipped identity binding, the bot will not reply - your message will be discarded (recorded for audit purposes only, message content is not saved).

Conversations with /issue

• Ask the agent anything - Chat with the Bot privately, or @ it in the group. A conversation is just an ordinary agent chat session, with the agent replying in a card.
• Create issue - Send /issue fix login jump, Multica will create this issue in the workspace, just like any new issue. Add a few lines after the title to describe it.
• Watch it work - The reply card will be continuously updated as the agent runs, and the progress and results are presented in place.

If the agent is offline (not connected when running) or archived, the Bot will reply with a brief status prompt instead of silently discarding your message.

• Connected Bots lists each Bot in the workspace and the agents it is bound to. This list is visible to all members.
• Disconnect Owner/Administrator only. After disconnection, the Bot stops receiving Feishu messages and the connection is destroyed; the installation record will be retained for auditing, and you can rebind the same agent later.

• Bind/Disconnect requires workspace Owner or Administrator. Members can see the list of connected Bots, but cannot see the binding or disconnecting operations.
• Conversation with Bot requires you to be a member of the workspace and have bound your Feishu identity. The rest were thrown away.
• For discarded messages, the integration does not save the message content - only a discard reason is recorded for auditing purposes.

During self-deployment, Feishu integration is turned off until you set the static encryption key. This key is used to encrypt each Bot’s app secret before it is stored in the database.

1. Generate a 32-byte key and set it to the API server:

   MULTICA_LARK_SECRET_KEY=<base64 encoded 32-byte key>
   

2. Restart the API. Before the key is set, Settings → Integration will display the prompt "Feishu integration is not enabled", and the Bind to Feishu entrance will also remain hidden.

**Supports both Feishu and overseas version of Lark. **Which cloud each Bot belongs to—Mainland China Feishu (open.feishu.cn) or the overseas version of Lark (open.larksuite.com)—will be automatically identified when you scan the QR code, recorded on that installation, and used for all calls to this Bot. The same deployment can serve both at the same time, so teams from both tenants can be bound directly without any additional configuration. MULTICA_LARK_HTTP_BASE_URL / MULTICA_LARK_CALLBACK_BASE_URL are reserved only as optional deployment-level overrides (for proxies or mocks); please leave them unset for normal operation, allowing each installation to connect to its own cloud. **Upgrading from a single cloud deployment? ** If you previously set these two variables to https://open.larksuite.com to run the overseas version of Lark, after the upgrade the service will automatically remark the existing installation as Lark region when it is started for the first time. You can then clear this override. Domestic Feishu deployment does not require any operations.

• Agents - Each Bot is bound to exactly one agent
• Chat - What does a Bot conversation correspond to in Multica?
• Issues - What is created by /issue
• Environment Variables - Complete self-deployment configuration reference