You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Idea] Telegram as a remote control for the whole team: drafts with Stop, private approvals, topics per Bot, status panel
#1399
I use DS Bot from Telegram every day and built the pieces below in a fork, on Bot API 10.1–10.4. Before turning any of it into issues and pull requests I'd like to know which parts fit DS Bot's direction. Each part is independent and gated by an optional platform capability, so the other platforms are unchanged.
1. Draft and Stop (private chats). While a Bot writes a step, the chat shows a live draft (sendRichMessageDraft, throttled), replaced by the final message. The draft carries Telegram's Stop button; Stop ends the Bot's whole running turn through the same path as /stop (stopChat / stopRoomWork). Groups get final messages only.
2. Private approval cards in groups. The bridge remembers who started a turn from Telegram (the Initiator). An approval for that turn in a group is sent as an ephemeral message only the Initiator sees, and only their presses count. No Initiator (timer, goal, another Bot, the computer) → a normal card. Unanswered for 5 minutes → becomes a normal group card.
3. One Telegram bot for the whole team (topics). A connection stops being bound to one Bot: each Telegram topic, in the private chat (topic mode) or in a forum supergroup (/bind, admins only), is bound to one Bot or one group chat. Each paired person has an access list (default: all), chosen when the pairing is accepted. The connection's current Bot becomes the default for messages outside topics, so existing connections keep working without changes. Topics follow renames and deletions.
4. Reply where asked. With several bindings for one Bot, output of a turn started in Telegram goes only to the place it was started from; turns started elsewhere (computer, timer, goal) go only to private chats, never to groups, controlled by a per-connection setting (all / cards only / nothing).
5. Status panel./status in a private chat posts and pins a small widget (Bot API 10.4) with the Bot's state, current tool, step and elapsed time, updated as it works, with a Stop button. In groups /status answers with a plain message.
This changes a design decision (a connection bound to one Bot), so I understand it needs your call. Which of these would you accept, and should any of them get a design note in docs/plans/ first?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
I use DS Bot from Telegram every day and built the pieces below in a fork, on Bot API 10.1–10.4. Before turning any of it into issues and pull requests I'd like to know which parts fit DS Bot's direction. Each part is independent and gated by an optional platform capability, so the other platforms are unchanged.
1. Draft and Stop (private chats). While a Bot writes a step, the chat shows a live draft (
sendRichMessageDraft, throttled), replaced by the final message. The draft carries Telegram's Stop button; Stop ends the Bot's whole running turn through the same path as/stop(stopChat/stopRoomWork). Groups get final messages only.2. Private approval cards in groups. The bridge remembers who started a turn from Telegram (the Initiator). An approval for that turn in a group is sent as an ephemeral message only the Initiator sees, and only their presses count. No Initiator (timer, goal, another Bot, the computer) → a normal card. Unanswered for 5 minutes → becomes a normal group card.
3. One Telegram bot for the whole team (topics). A connection stops being bound to one Bot: each Telegram topic, in the private chat (topic mode) or in a forum supergroup (
/bind, admins only), is bound to one Bot or one group chat. Each paired person has an access list (default: all), chosen when the pairing is accepted. The connection's current Bot becomes the default for messages outside topics, so existing connections keep working without changes. Topics follow renames and deletions.4. Reply where asked. With several bindings for one Bot, output of a turn started in Telegram goes only to the place it was started from; turns started elsewhere (computer, timer, goal) go only to private chats, never to groups, controlled by a per-connection setting (all / cards only / nothing).
5. Status panel.
/statusin a private chat posts and pins a small widget (Bot API 10.4) with the Bot's state, current tool, step and elapsed time, updated as it works, with a Stop button. In groups/statusanswers with a plain message.This changes a design decision (a connection bound to one Bot), so I understand it needs your call. Which of these would you accept, and should any of them get a design note in
docs/plans/first?Implementation (fork, based on
main): https://github.com/Nombah501/DS-Bot/tree/telegram-bridgeAll reactions