All pages

Docs · AI features

Telegram

Availability: macOS.

The Telegram bridge lets you talk to the TRMNLY agent from your phone. Register one or more Telegram bots; each bot gets its own token, scope (one project or all projects), and paired-user allowlist. Each chat runs a full agent session on your Mac, with replies and tool activity streamed back into the conversation.

The bridge long-polls the Telegram Bot API, so it works from behind NAT with no webhook, server, or tunnel. Bots stop the moment TRMNLY quits.

Setup

  1. In Telegram, create a bot with @BotFather and copy its token.
  2. Open the right sidebar's Plugins tab → Drive from Telegram and click + to add a bot. Pick a scope: a single project, or all projects.
  3. Expand the bot's row and paste the token. It's stored in the macOS Keychain, never on disk in plaintext.
  4. Flip the row's toggle on.

Pairing

Nobody can talk to a bot until they pair with it:

  1. Click Generate pair code in the bot row. Codes expire after about ten minutes and burn after a few wrong attempts.
  2. In Telegram, send /pair <code> to the bot.

Paired accounts are listed in the row; Remove revokes one at any time.

What you can do

Send a plain message and it becomes a user turn in an agent session pinned to the chat's project (all-projects bots ask you to pick one with /project first). Commands:

Command What it does
/projects List available projects
/project <name> Bind this chat to a project
/new Start a fresh session
/stop Cancel the current run
/help List commands

Bots locked to a single project skip /projects and /project. Only text messages are supported. Sessions started from Telegram are stored like any other, so the transcript also shows up in the in-app agent sidebar.

Safety and approvals

Approvals never leave the Mac. A WRITE tool that needs confirmation pauses the run and posts "needs approval on Mac" in the chat — you approve or deny from the approval card in TRMNLY, not from Telegram. Tool calls are narrated in the chat (running / failed / denied) so you can watch what the agent does remotely.

Settings → Security lists Telegram as a scripting source with its own off-switch, always-confirm toggle, and rate limit. Per-bot scoping limits the blast radius: a leaked token or hijacked chat can only reach the projects that bot was given.