logo
icon

OpenAB Telegram Bundle

All-in-one Telegram bot powered by OpenAB + Kiro. Deploys the OAB agent and the Telegram gateway together — fill in one bot token and you're done. No separate gateway setup, no manual config.toml edits. Source: https://github.com/openabdev/openab

template cover
展開済み0 回
発行者zeaburZeabur
作成日2026-05-21
ソースソースを表示
最小構成2 コア4 GB
推奨構成4 コア8 GB
タグ
AIDeveloper ToolsTelegram

サービス

service icon

openab

ghcr.io/openabdev/openab:stable
service icon

openab-gateway

ghcr.io/openabdev/openab-gateway:0.5.1

OpenAB Telegram Bundle

One-click OpenAB deployment for Telegram — bot agent + webhook gateway bundled together. Just fill in your Telegram bot token.

Telegram ──POST──▶ ┌──────────────────┐ ◀──WebSocket── ┌────────────┐
                   │  openab-gateway  │                │   openab   │
                   │  (telegram only) │                │  (Kiro CLI) │
                   └──────────────────┘                └────────────┘
                      public HTTPS                       internal only

What's deployed

ServicePurposePublic
openabOAB agent running Kiro CLINo
openab-gatewayTelegram webhook → WebSocket bridgeYes (auto HTTPS)

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

Setup

1. Create a Telegram Bot

  1. Open @BotFather in Telegram
  2. Send /newbot and follow the prompts
  3. Username you chose (e.g. my_zeabur_bot, must end in bot) → paste into Bot Username
  4. Bot token that follows (e.g. 123456:ABC-DEF...) → paste into Telegram Bot Token
  5. For group/supergroup use: send /setprivacy → Disable so the bot can see all messages (required for @mention gating)
  6. For supergroups with forum topics (auto thread-per-conversation): add the bot to the group → group settings → Administrators → enable Manage Topics

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. A public HTTPS domain is auto-assigned to the gateway service.

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

Send a message to your Telegram bot. The gateway receives it, forwards it to OAB via WebSocket, and OAB replies through the gateway.

The Telegram webhook is registered automatically by an init container in the openab-gateway service at startup — look for openab-gateway: telegram webhook registered → https://... in the gateway logs. No manual curl setWebhook needed.

If you ever need to re-trigger it (e.g. after rotating the bot token or changing the gateway domain), open the openab-gateway service page in Zeabur Dashboard — under Instructions, the Re-register Telegram Webhook curl is pre-filled.

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.

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 Gateway for LINE, Feishu/Lark, Google Chat, MS Teams, WeCom.