Feature Request: Telegram Forum Topics Support for PicoClaw
🎯 The Goal / Use Case
The goal is to provide PicoClaw users with the same organizational power available in OpenClaw. Specifically, support for Telegram Forum Topics (Threads) is needed to isolate conversation contexts for different agents or tasks within a single forum-enabled group. This allows PicoClaw to act as a centralized "Control Hub" where each topic can be bound to a specific agent or session, preventing message history from bleeding across different workstreams.
💡 Proposed Solution
Implement message_thread_id handling within the PicoClaw Telegram adapter:
- Session Isolation: Include the
thread_id in the session key generation (e.g., chatId:topicId) so that each topic maintains its own isolated context/history.
- Agent Routing: Allow per-topic agent overrides via configuration (similar to OpenClaw's
topicAgentOverrides), enabling different topics to automatically route to different specialized agents.
- ACP Support: Enable ACP (Agentic Control Plane) sessions to spawn within and bind to specific topics, ensuring all follow-up execution remains within the correct thread.
🛠 Potential Implementation (Optional)
- Update
TelegramInboundContext to extract and normalize message_thread_id from incoming updates.
- Modify the
sessionKey resolver to be thread-aware.
- Expand the configuration schema to support a
topics map under group configs, allowing for topic-specific agentId, systemPrompt, and skills.
- Ensure all outbound
sendMessage calls correctly pass the message_thread_id to maintain thread integrity.
🚦 Impact & Roadmap Alignment
🔄 Alternatives Considered
The current alternative is creating multiple separate groups for different agents, which is difficult to manage and clutters the Telegram chat list.
💬 Additional Context
Special handling should be considered for the "General" topic (ID 1), as Telegram handles it uniquely. This feature is critical for users who manage complex workflows with multiple specialized agents (e.g., mail processing, system admin, personal assistance) through a single bot interface.
Feature Request: Telegram Forum Topics Support for PicoClaw
🎯 The Goal / Use Case
The goal is to provide PicoClaw users with the same organizational power available in OpenClaw. Specifically, support for Telegram Forum Topics (Threads) is needed to isolate conversation contexts for different agents or tasks within a single forum-enabled group. This allows PicoClaw to act as a centralized "Control Hub" where each topic can be bound to a specific agent or session, preventing message history from bleeding across different workstreams.
💡 Proposed Solution
Implement
message_thread_idhandling within the PicoClaw Telegram adapter:thread_idin the session key generation (e.g.,chatId:topicId) so that each topic maintains its own isolated context/history.topicAgentOverrides), enabling different topics to automatically route to different specialized agents.🛠 Potential Implementation (Optional)
TelegramInboundContextto extract and normalizemessage_thread_idfrom incoming updates.sessionKeyresolver to be thread-aware.topicsmap under group configs, allowing for topic-specificagentId,systemPrompt, andskills.sendMessagecalls correctly pass themessage_thread_idto maintain thread integrity.🚦 Impact & Roadmap Alignment
🔄 Alternatives Considered
The current alternative is creating multiple separate groups for different agents, which is difficult to manage and clutters the Telegram chat list.
💬 Additional Context
Special handling should be considered for the "General" topic (ID 1), as Telegram handles it uniquely. This feature is critical for users who manage complex workflows with multiple specialized agents (e.g., mail processing, system admin, personal assistance) through a single bot interface.