From df40dc955e50ad369223b9620f3a7469292cd805 Mon Sep 17 00:00:00 2001 From: devshilov Date: Sun, 2 Aug 2026 02:18:19 +0500 Subject: [PATCH] adr: Telegram as another agent surface Co-authored-by: Cursor --- adrs/telegram.md | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 adrs/telegram.md diff --git a/adrs/telegram.md b/adrs/telegram.md new file mode 100644 index 000000000..c025335a2 --- /dev/null +++ b/adrs/telegram.md @@ -0,0 +1,9 @@ +# Telegram as another way to talk to the agent + +We already have Slack and the web UI. I'd like Telegram too. + +First cut can be small: private DMs only. Link your Telegram account from the web UI with a one-time code so the same person is the same principal across surfaces. Groups, files, and fancy approval buttons can wait. + +I wouldn't shove this into the in-process Slack plugin. A small separate service that long-polls the bot API and talks to core like the other surface plugins feels cleaner, and keeps Telegram opt-in behind a BotFather token. + +Curious if that's the shape you'd want before anyone burns tokens on it.