Skip to content

adr: Telegram as another agent surface #108

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gauss2302 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

adr: Telegram as another agent surface #108

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions adrs/telegram.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.