Replies: 4 comments 10 replies
-
|
I really like the current features, but it is a bit inconvenient to use a single private chat bot when I am developing multiple projects and switching between sessions. I was wondering if you have considered using a Private Group format. This way, no one else can access it, and I could create different topics within the group to categorize my projects. By switching sessions directly within the project topics, it should significantly reduce the number of operations required to switch back and forth. While this might deviate slightly from the original design direction of a private DM bot, I think it could be a valuable extension of the current functionality. In theory, only the buttons below the keyboard cannot be displayed directly; everything else should be usable as an inline button. However, can this part be implemented within a pinned message instead? |
Beta Was this translation helpful? Give feedback.
-
|
Group Thread is a better alternative. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for suggestion. A group + topics setup is possible in theory, but there are important limits. If we run several sessions in parallel across different threads, we can hit Telegram limits much faster (for example: about 1 message per second per chat, about 20 messages per minute in groups, and around 30 messages per second for bulk sending before 429 rate-limit errors). For this bot, with frequent status/tool updates, this matters a lot. Another key point is the bottom reply keyboard. It is one of the main features of this bot. Moving away from it would require more slash commands and more inline-only flows, which is not always convenient. I want to keep the command list small and simple. Right now my main focus is stability, better test coverage, architecture improvements, and missing OpenCode features. So at this stage I’m not planning to change the core concept. This bot was designed as a “single OpenCode CLI window” inside Telegram, and I want to keep that experience. |
Beta Was this translation helpful? Give feedback.
-
|
Roger. |
Beta Was this translation helpful? Give feedback.
-
|
Btw, bottom reply keyboard works well in group chat. and The backslash command works just as well. |
Beta Was this translation helpful? Give feedback.
-
|
Now Telegram bots support threading! Threading can be enabled in BotFather, would be great to allow parallel execution of sessions in threads |
Beta Was this translation helpful? Give feedback.
-
|
@IsroilovA thanks for this idea. Using threads for different sessions could be convenient, I will look how is works. I don't want to give up the direct messages mode but maybe it could be thread mode which can be activated in settings. @shanekunz now works on the similar feature #38 you can try it and give feedback to him. I suggest to make fork of this repo and develop it in different way. |
Beta Was this translation helpful? Give feedback.
-
|
@IsroilovA @grinev the current PR #38 version has attempts to gracefully handle the 20 messages per minute per group (groups map to a repo on your computer in my branch), and it may change the batch size of messages depending on how big the queue grows; however, I have not stress tested it that much. If you test my branch, you should expect multithreading to add significant latency to the delivery of your opencode responses. |
Beta Was this translation helpful? Give feedback.
-
|
Pretty close to launching the fork. I pulled in the latest |
Beta Was this translation helpful? Give feedback.
-
|
The group topics fork has been published with a blessing and some ideas from @grinev It supports creating one group per local repository, and each group topic as a separate opencode session. Each group's "general" channel acts as a launcher and will create new group topics for you and sync the name of the topic with the opencode session name. Parallel execution is supported. Each group requires one-time manual setup to create the group, add the bot, make the bot an admin, and enable topics. Automatic group creation will not be supported because it requires calling a separate Telegram API on behalf of the user's account which adds security risks and complexity. https://github.com/shanekunz/opencode-telegram-group-topics-bot |
Beta Was this translation helpful? Give feedback.
-
|
I think you should open issues on the new fork because I found one issue about Poll question, I will try to contribute to your fork |
Beta Was this translation helpful? Give feedback.
-
|
@EvanDbg thanks for testing. "Issues" tab now opened, fire away. |
Beta Was this translation helpful? Give feedback.
-
|
Can we upgrade the project to add a mode that supports usage in OpenClaw?OpenClaw integrates with numerous IM Channels, allowing users to interact with Opencode within their preferred instant messaging platforms. |
Beta Was this translation helpful? Give feedback.
-
|
This project is about Telegram bot for OpenCode. The emphasis is on a responsive UI in Telegram, adding one more IM support needs the same amount of work to keep UI at the same level. So I don't have this in plans. Now I'm focusing to add more features in current implementation |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone! 👋
Do you have an idea on how to make the bot better? This is the perfect place to share it!
To help us understand your idea, please include a few simple details when you post:
The problem: What issue are you trying to solve?
The solution: How exactly should the new feature work?
Feel free to share any ideas, big or small. And please use the 👍 reaction to vote for the features you like the most!
Beta Was this translation helpful? Give feedback.
All reactions