Forum topic session isolation

[penatechnologies]

Problem

Distinct Telegram chats were already isolated upstream by chat_id, but forum topics inside the same Telegram supergroup were not. They shared the same session key and the same interrupt bucket, which caused topic context bleed and cross-topic interruption. The tool-side target directory also collapsed topics down to the parent chat, so explicit topic sends were not possible.

• include Telegram thread_id in non-DM session keys so forum topics inside one supergroup do not share context
• key active gateway interrupts by the canonical session key instead of raw chat_id
• preserve Telegram topic routing for replies, cron origin delivery, transcript mirroring, and tool-based sends
• expose Telegram forum topics as distinct send_message targets and support explicit telegram:chat_id:thread_id addressing

Basically: Is it possible to segment/isolate forum/group topics so we can have specific agents/models/memory/sessions exclusive to that particular topic?

[penso]

This has been implemented across several recent changes. Here's what landed:

Session isolation

Forum topics inside a Telegram supergroup now get their own session key. The key format is telegram:<account_id>:<chat_id>:<thread_id> for topics (vs telegram:<account_id>:<chat_id> for regular chats). This means each topic has its own conversation context, memory, and model binding — no more cross-topic bleed.

The channel_sessions table was updated to include thread_id in the primary key, so you can assign different sessions (and therefore different agents/models) to individual topics.

Reply routing

All outbound paths — replies, streaming, error messages, cron delivery, transcript mirroring, and tool-based send_message — now route to the correct forum topic using a composite chat_id:thread_id address. The Telegram outbound layer parses this and applies message_thread_id() so replies land in the right thread.

Interrupt isolation

Active gateway interrupts are now keyed by the canonical session key (which includes thread_id) instead of the raw chat_id. Interrupting a conversation in one topic won't cancel a run in another topic within the same supergroup.

Explicit topic addressing

Forum topics are exposed as distinct send_message targets. You can address a specific topic with telegram:<chat_id>:<thread_id> from tools.

Stream deduplication

The stream completion tracker now includes thread_id in its dedup key, so finishing a streaming response in one topic doesn't block delivery in another.

---

In short: yes, you can now have specific agents, models, memory, and sessions exclusive to each forum topic. Each topic behaves as its own independent channel.