Telegram — BotBandit

Drive your crew from a chat. The Telegram bot gives each chat its own session, so you can kick off work, answer approval prompts, and read results from your phone.

Enable it

The bot is a resident service: it runs with the daemon rather than being attached to a profile. Enabling it is just configuring a token.


profiles:
  telegram:
    provider: alibaba
    extensions: [systemPrompt, baseTools, skills, approval, memory]
 
extensions:
  telegram:
    token: env:BOTBANDIT_TELEGRAM_TOKEN
    # Who may talk to the bot — a list, or an env:/literal comma-separated string.
    # Empty or unset means the bot ignores everyone.
    allowedUsers: [123456789]
    # Profile used for per-chat sessions. Defaults to "telegram".
    # profile: telegram

Then restart the daemon:


boba daemon restart

allowedUsers is fail-closed — unset means nobody, not everybody. Set it to your own numeric Telegram user ID. A bot token is a bearer credential for anyone who finds it, so keep it in an env var (env:NAME) rather than inline.

There is no boba telegram command — configuring the token is what turns the service on, and a missing token leaves it quietly disabled rather than failing daemon startup.

Using it

Message the bot and it creates (or reuses) a session for that chat. The session is a normal Boba session: it shows up alongside the rest in the TUI and the web UI, and it survives daemon restarts.

/compact compacts the chat’s conversation when it grows long.