[Feature request] Support for Group Chat Topics (Forum) - Multiple Concurrent Sessions

[dinhkao]

Problem

Currently, the bot only supports one active chat session at a time. Users must manually switch between different conversations, which is limiting when working with multiple topics or projects simultaneously.

Proposal

Add support for Telegram Group Chat Topics (Forums) where each topic thread acts as an independent session with its own isolated context and conversation history.

Done criteria (optional)

No response

[m407]

Huge logic rewrite needed, I think. Did same thing for my telegram chatgpt bot.

[grinev]

@dinhkao thanks for feedback. This feature is out of concept of this project. Please look to https://github.com/grinev/opencode-telegram-bot/blob/main/CONCEPT.md

You can try this fork https://github.com/shanekunz/opencode-telegram-group-topics-bot

[insign]

Add support for Telegram topics and message threads

Telegram supports topic-based conversations in forum-enabled supergroups, as well as topics in private bot chats. Each topic is identified by a "message_thread_id".

It would be useful for the framework to support topics as first-class conversation contexts, so messages from different topics are not mixed together.

Suggested behavior

• Expose "message_thread_id" in incoming message and update objects.
• Allow sending replies to a specific topic.
• Use both "chat_id" and "message_thread_id" when identifying conversation or session state.
• Support creating, editing, closing, reopening, and deleting forum topics when permitted by the Telegram Bot API.
• Keep backward compatibility for chats that do not use topics.

A possible conversation identifier could be:

telegram:{chat_id}:{message_thread_id}

For messages without a thread, the framework could continue using only the "chat_id".

This would make it easier to build bots that maintain independent context, history, and workflows inside each Telegram topic.

[bilogic]

thanks for feedback. This feature is out of concept of this project. Please look to https://github.com/grinev/opencode-telegram-bot/blob/main/CONCEPT.md

@grinev I understand your approach to keep it narrowly scoped, but I think that makes us "blind" to alot of possibliities and experience that might shift the paradigm.

For example, I came to realize that our desktop/window interface (even herdr) is one of the main problem because wasn't designed to handle AI, which turns around alot faster, requiring us to multitask alot more than we are able to.

The fork is hundreds of commits apart, this means contributiors will likely choose 1 or the other, not both.

From the name of this repo, I think your goal is to make opencode usable anywhere, specifically on telegram, why not make full use of the telegram features from day 1?

[grinev]

@bilogic Let me write again what I’ve already written several times. I understand that it would be great to work with each session in a separate thread. But the project was conceived differently - as a single session in one dialogue with the option to switch to another. The architecture is designed for that. There’s a lot of work to be done to rework it, and that’s not even the main problem; the main problem is that it will be difficult to test and debug all of this because of the parallel sessions. Plus, the Telegram rate limits still won’t allow you to run multiple sessions in parallel and track progress in real time.

For me, this is a hobby project, and I take on the amount of tasks I know I can handle. Also, it’s better to have fewer features that work stably than many that have bugs.

By the way, the bot now allows you to run multiple sessions in parallel from your phone. Check out the /detach command — it will disconnect you from the current session, and a notification will be sent to the chat that the session has ended, along with a button to switch to that session.

[m407]

@grinev /detach command is really greate!