Telegram¶
Chat with your agent from a Telegram DM or group.
How Telegram differs from Slack¶
Telegram uses the same access model as Slack: the binding is the authorization, so anyone in a bound chat drives the agent under the agent's own credentials, with no login needed. See who can drive the agent.
What differs is everything around it — Telegram has no identity linking, so group admin is the gate on the in-chat commands; messages relay as text only; and a first message to a sleeping agent gets no heads-up — Telegram just goes quiet until the agent is up, where Slack tells you it's waking.
Connect a chat¶
- Add the bot to the chat (or open a DM with it).
- Send
/bind. In a group, only admins can do this — anyone else gets "Only group admins can/bind." - Follow the login link, then pick one of your own agents.
- The bot confirms in the chat.
/start also counts as bind intent, so deep links and Telegram's Start button work.
| Command | What it does |
|---|---|
/bind |
Connect one of your agents to this chat (group admins only) |
/unbind |
Release the binding (group admins only) |
/ambient on\|off |
Turn ambient mode on or off in a group (group admins only) |
/ambient |
Report whether ambient mode is on |
All three are published to Telegram's own command menu, so typing / in the chat lists them with a
description — there's no separate help command to find. In a group with more than one bot, address a
command to this one as /bind@<botname>.
These commands are Telegram's own, not /dam's
Telegram's commands are bare: /bind, not /dam bind. Slack is different — there the agent is driven
with the /dam slash command, because a Slack app owns one command name and namespaces
its verbs underneath it.
One agent per chat
A chat binds to one agent. Binding an already-connected chat is refused with "This chat is
already connected to an agent. Send /unbind first to reconnect." The same agent can be
bound to several chats — as it can to several Slack conversations.
The login link expires after about 10 minutes — send /bind again if you miss the window.
Send /unbind in the chat to release the binding; the bot confirms in the chat.
You can also disconnect from DAM: open the agent, go to Channels, and click Disconnect on
the chat in the Telegram card. The bot posts a farewell note in the chat before the binding goes. The
card lists the chats already connected and links the bot so you can add it somewhere new — but
connecting itself always happens in the chat, with /bind.
If Telegram isn't listed
Channels only shows what your operator has set up. Where Telegram isn't wired up, its card isn't there — ask them.
How the agent is triggered¶
| Surface | What triggers a reply |
|---|---|
| DM | Every message |
| Group | An @mention of the bot, or a reply to one of its messages. With ambient mode on, every message (the agent decides whether to answer) |
Unbound groups stay silent, so the bot doesn't spam every chat it's been added to. In an unbound
DM it replies "This chat isn't connected to an agent. An admin needs to send /bind."
Ambient mode¶
Ambient mode is off by default, so in a group the agent answers only messages that mention it or
reply to it. A group admin turns it on with /ambient on — the agent then reads every message in the
chat and may chime in without being mentioned — and back off with /ambient off. It doesn't apply in a
DM, where every message already reaches the agent. If the bot has Telegram's Group Privacy setting
on, Telegram doesn't show it un-addressed messages, and turning ambient on tells you so.
Inbound is text only
Telegram messages relay as text. Images and other attachments are not passed to the agent — unlike Slack, which reads images and hands over files. Paste the content you need the agent to see.
That's about messages coming in. Going the other way, an agent posting to Telegram of its own accord can attach a single file to its message.
Sessions¶
One chat, one session. A Telegram chat maps to a single persistent session, so a group
conversation continues in one place rather than splitting per reply — unlike
Slack, where each thread gets its own session. (In a forum group the
binding covers the whole group — /bind in any topic connects all of them — but each topic keeps its
own session.)
A burst of messages gets one answer, as on Slack: the agent waits for a short pause, then answers everything that arrived together. Something sent while it's already working is handed to that turn where the harness supports it; otherwise it becomes the next turn rather than a second answer racing the first. Bursts are grouped per chat, not per person — so in a group, messages from several people that land together are answered together.
As on Slack, nobody is there to answer a harness permission prompt, so a tool the agent would have to ask about is refused; see what else to expect.
A Telegram agent can post on its own — a scheduled result, an alert — but only into chats bound to it. Unlike Slack, it can't reach a chat it isn't connected to.
Troubleshooting¶
| Problem | Solution |
|---|---|
"Only group admins can /bind" |
Only a chat admin can connect a group. Ask one to run it |
"Only group admins can /unbind" |
Ask a chat admin to run /unbind in the chat |
| "This chat is already connected to an agent" | Send /unbind first, then bind again |
| "This chat isn't connected to an agent" | Run /bind to connect one of your agents |
| Bot silent in a group | Make sure you @mention it or reply to it, and that the chat is bound — or turn on /ambient |
| The login link didn't work | It expires after ~10 minutes — send /bind again |
| An attached image was ignored | Telegram relays text only. Paste the content instead |
| Asked to accept Terms of Use in a DM, or silence in a group | Whoever bound the chat must accept the terms in DAM before any turn runs — turns use that person's consent, not yours. A DM says so; in a group nothing is posted and the bot just stays quiet |