Telegram · Briglia CLI

Set it up

In Telegram, message @BotFather → /newbot → follow the prompts → copy the token.
Message @userinfobot to get your numeric chat ID (a number — letters mean it's a username).
Run briglia setup → section “Telegram” and paste both. The token is checked live.
Start Briglia (briglia, briglia daemon, or the service) and send your bot a message.

One chat, nobody else

Briglia answers only the paired chat ID and silently ignores every other message, group or user. There is no allowlist to manage. To move to a different bot later, use /switchbot — guided, with a confirmation code.

What you can send

Text — including while Briglia is busy: messages that arrive mid-turn are delivered at the next pause, authenticated so a document can't impersonate you.
Voice notes — transcribed with your OpenAI key.
Photos — seen directly by a vision model (or OCR'd first for text-only models).
Documents (PDF, DOCX, TXT…) — saved to Briglia's landing zone; Briglia reads them deliberately with its file tools, so a big PDF doesn't flood the context.

The command menu

Type / in Telegram to see the short menu: /stop, /status, /prune, /upgrade, /commands. /commands lists the full standard set — models, system, account. The same commands work in the terminal chat; the two surfaces share one command set. Full list in Commands.

Briglia writes first

When a reminder fires, a watcher reports, a background job finishes or an email arrives, Briglia messages you on Telegram without being asked — that is the point of an always-on setup. Long-running work can also send you interim notes mid-task.

Good to know

/upgrade and /restart refuse while a turn is running — send /stop first.
Briglia acknowledges each Telegram update only after it is durably stored, so a crash or power failure doesn't lose your message — at worst you see it processed twice.
Privacy mode: /hide stops Briglia from echoing message bodies to the local chat surfaces; /show reverts.