openclaw - 💡(How to fix) Fix Feature: option to route specific group chats to main agent session [1 comments, 2 participants]

TL;DR

Implement a configuration option to route messages from specific groups into the main agent session, allowing for continuity with DM conversations.

Guidance

• Consider adding a groupsAsMain config option or a per-group session: main override to enable routing of group messages into the main session.
• Evaluate the proposed JSON configuration example to determine if it meets the requirements for routing group messages into the main session.
• Assess the feasibility of implementing real-time context sharing between DM and group conversations, potentially building upon the existing memory file workarounds.
• Review the current multi-agent setup to ensure that the proposed solution does not introduce conflicts or inconsistencies between agents.

Example

The proposed JSON configuration example provides a potential solution:

{
  "channels": {
    "telegram": {
      "groups": {
        "-5033226593": {
          "session": "main",
          "requireMention": false
        }
      }
    }
  }
}

This example demonstrates how to specify a group ID and configure it to use the main session.

Notes

The implementation of this solution may require modifications to the underlying architecture of the agent and its interaction with the Telegram channel. Additionally, ensuring seamless context sharing between DM and group conversations may pose technical challenges.

Recommendation

Apply a workaround by implementing the proposed groupsAsMain config option or per-group session: main override, as it addresses the specific use case of maintaining continuity between DM and group conversations in small private groups.