OpenAB Feishu/Lark Bundle

One-click OpenAB deployment for Feishu / Lark — bot agent + WebSocket gateway bundled together. Just fill in your App ID and App Secret.

Feishu/Lark ◀──Long Connection──▶ ┌──────────────────┐ ◀──WebSocket── ┌────────────┐
              (outbound from gw) │  openab-gateway  │                │   openab   │
                                 │ (feishu only)    │                │  (Kiro CLI) │
                                 └──────────────────┘                └────────────┘
                                   internal only                       internal only

No public HTTPS, no webhook URL, no firewall config — the gateway initiates an outbound WebSocket connection to Feishu Open Platform.

What's deployed

Service	Purpose	Public
openab	OAB agent running Kiro CLI	No
openab-gateway	Feishu Long Connection ↔ OAB WebSocket bridge	No

No PVC sharing, no manual config.toml edits. The agent's config.toml is generated on first boot with the [gateway] block pre-wired to ws://openab-gateway:8080/ws and platform = "feishu".

Setup

1. Create a Feishu / Lark App

1. Go to open.feishu.cn (China) or open.larksuite.com (international) → Create Custom App.
2. Enable the Bot capability.
3. Event Subscriptions → choose Long Connection (WebSocket) mode → subscribe to the im.message.receive_v1 event.
4. Permissions & Scopes → grant:
   • im:message
   • im:message:send_as_bot
   • contact:user.base:readonly
5. Credentials & Basic Info → copy App ID → paste into Feishu/Lark App ID.
6. Same page → copy App Secret → paste into Feishu/Lark App Secret.
7. If using Lark international, set Feishu/Lark Domain to lark (otherwise leave at feishu).
8. Publish the app version (Feishu / Lark requires a published version before the bot is reachable).

2. (Optional) Get a Kiro API Key

If you have a paid Kiro subscription, go to kiro.dev → Settings → API Keys → create a key and paste it into KIRO_API_KEY. Free tier users skip this and authenticate post-deploy in step 4.

3. Deploy

Click deploy. No domain is assigned — both services run on the internal network.

4. Authenticate Kiro via Device Flow (free tier only)

Skip if you set KIRO_API_KEY in step 2.

After the openab service is running, open its terminal in Zeabur Dashboard and run:

runuser -u agent -- kiro-cli login --use-device-flow

Follow the URL and code to authorize in your browser.

5. Test

Open the bot inside Feishu / Lark and send a direct message. The gateway receives it via its outbound Long Connection, forwards it to OAB, and OAB replies through the gateway.

Group chats: invite the bot, then @<your-bot> hello. By default Feishu requires @mention in groups (FEISHU_REQUIRE_MENTION=true). DMs do not need @mention.

Customization

• /home/agent/.config/openab/config.toml — OAB config (sessions, reactions, etc.). Created on first boot from a built-in template with the [gateway] block pre-wired. To regenerate, delete and restart.
• Image tags — bot tracks the floating stable channel (ghcr.io/openabdev/openab:stable) and auto-updates with each OpenAB stable release. Gateway is pinned at ghcr.io/openabdev/openab-gateway:0.5.1 (no :stable tag yet). To pin or bump, change the tag in Zeabur Dashboard → Service → Settings. Available tags: OpenAB / Gateway.
• Advanced env — set on openab-gateway: FEISHU_ALLOWED_GROUPS / FEISHU_ALLOWED_USERS (comma-separated IDs to restrict access), FEISHU_REQUIRE_MENTION=false (auto-respond in groups without @), FEISHU_ALLOW_BOTS=mentions|all (let other bots @ mention this bot).

Want a different agent backend?

This bundle uses Kiro as the default agent. For Claude / Codex / Cursor / Gemini / OpenCode / Hermes / Grok, deploy the corresponding bot template separately together with the standalone OpenAB Gateway.

Want a different platform?

See OpenAB Telegram Bundle or the standalone OpenAB Gateway for Telegram, LINE, Google Chat, MS Teams, WeCom.

Links

• OpenAB GitHub
• Feishu/Lark Setup Guide
• Standalone OpenAB Gateway Template