Telegram
Lobu’s Telegram adapter supports direct chats, group interactions, and interactive workflows.
Under the hood, Lobu uses the Telegram Bot API via @chat-adapter/telegram.
C
Coding
online
List open PRs in lobu-ai/lobu12:01
Can't reach github.com — not in the agent's allowed domains.
Grant access?12:01
Allow for 1 hour12:01
Added github.com to allowed domains.
3 open PRs in lobu-ai/lobu:
• #214 Fix worker memory leak
• #219 Telegram adapter retries
• #223 Add Bedrock provider12:01
O
Ops Assistant
online
Summarize my active Linear sprint12:01
I need the `linear` skill to query Linear.
It bundles the Linear MCP and handles OAuth via Lobu.12:01
Go ahead12:01
Installed and connected.
Sprint "Week 15" (68% done):
• 11 merged, 3 in review, 2 todo
• Blocked: AUTH-234 (design)
• At risk: API-89 (due tomorrow)12:01
A
Assistant
online
Switch to Claude Sonnet12:01
You can change the model from your settings — opens a scoped page with your current agent config.12:01
Done — set to claude-sonnet-4-612:01
Now running on claude-sonnet-4-6 via OpenRouter.
Next messages will use the new model.12:01
- Create a bot with @BotFather on Telegram and copy the bot token.
- Run
lobu connections add telegramto add the connection (prompts for the bot token), or runlobu initto scaffold a new project and pick Telegram in the wizard. - Start the stack with
lobu run -d— the bot starts receiving messages immediately.
Configuration
Section titled “Configuration”| Field | Required | Type | Description |
|---|---|---|---|
botToken | No | string | Telegram bot token from BotFather. Falls back to TELEGRAM_BOT_TOKEN env var. |
mode | No | auto | webhook | polling | Runtime mode: auto (default), webhook, or polling. |
secretToken | No | string | Webhook secret token for x-telegram-bot-api-secret-token verification. |
userName | No | string | Override bot username. |
apiBaseUrl | No | string | Custom Telegram API base URL. |
Connection Settings
These settings apply to all platform connections and are passed in the settings object.
| Field | Required | Type | Description |
|---|---|---|---|
allowFrom | No | string[] | User IDs allowed to interact with this connection. Omit to allow all; empty array blocks all. |
allowGroups | No | boolean | Whether group messages are allowed (default true). |
userConfigScopes | No | string[] | Scopes that end users are allowed to customize. Empty = no restrictions. |
Features
Section titled “Features”- Long-polling or webhook handling for receiving messages.
- Inline keyboard interactions for structured choices and approvals.
- Platform-scoped settings links for authentication and configuration flows.
- Thread/context routing across DMs and group chats.
- File handling for documents and media attached in Telegram messages.
Typical Use Cases
Section titled “Typical Use Cases”- Personal AI assistant in Telegram DMs.
- Group copilots with mention-based interaction patterns.