Skip to content

v0.3.0 — Telegram

Choose a tag to compare

View all tags
@rullopat rullopat released this 28 May 17:50
v0.3.0
c8c66a9

Minor release. Three packages bumped in lockstep and published to npm with provenance:

What's new

This release is all about Telegram. Bazilion can now run a Telegram bot that gives each agent its own forum topic inside a single supergroup, with two-way chat and a dedicated ⚙ bazilion control-plane topic — so you can talk to your agents from your phone.

  • One topic per agent, two-way chat. Agents live in a Telegram forum supergroup: typing in an agent's topic runs a turn, and its reply mirrors back into the same topic with a "typing…" indicator and a 👀 reaction on your message. Messages sent while the agent is busy are queued and answered together.
  • Setup + preflight. Connect a bot token + supergroup chat ID from the web (/config/integrations/telegram) or the CLI (bazilion telegram config set). A preflight health check verifies bot identity, supergroup reachability, that forum Topics are enabled, that the bot has Manage Topics, and that Privacy Mode is off — each failed check comes with a fix hint. Activation is automatic and idempotent.
  • Spawn and bind from anywhere. From Telegram (/spawn, /spawn_team, /talk), the web agent page (bind a topic), or bazilion telegram bind. Each agent gets a named topic with a profile-derived icon; per-group name templates control titles and propagate renames.
  • Access control (trust-on-first-use). While the allowlist is empty, the first user to message the bot becomes the owner; everyone else is blocked until allowed. Owners manage members with /allow / /deny (by numeric id — /whoami reveals yours), plus the web Access control card and bazilion telegram allow|deny|allowed.
  • Multimodal inbound (bounded). Inbound photos, documents, and voice are downloaded into the agent's home and referenced by path for the turn, up to Telegram's 20 MB bot-download limit.
  • Resilience. Per-agent inbound/outbound rate budgets, a per-supergroup outbound send queue with 429 backoff, a polling stall-watchdog that self-restarts, supergroup-migration detection with a one-click Reconnect, and lazy reconciliation when a human deletes a topic.

Docs

A full step-by-step setup guide — including the manual BotFather and forum-supergroup steps — is on the new docs site: https://bazilion.com/docs/telegram/

Install

npx bazilion serve

Upgrading from 0.2.1

No breaking changes. New DB migrations for the Telegram tables run automatically on bazilion serve. Telegram is entirely opt-in — nothing changes until you configure a bot under /config/integrations/telegram.

Notes

Assets 2
Loading