openclaw - 💡(How to fix) Fix [Bug]: [WeCom] DM消息隔离失效 - 不同用户的私聊被路由到同一会话 [1 comments, 2 participants]

Fix Plan

To resolve the issue of incorrect routing of private chat messages in the WeCom channel, we need to modify the resolveAgentRoute function to correctly handle private chat (DM) sessions.

Step-by-Step Solution:

1. Update the resolveAgentRoute function to check if the incoming message is a private chat message.
2. Create a unique session ID for each user's private chat.
3. Route private chat messages to their respective user sessions instead of the default agent:main:main session.

Example Code:

def resolveAgentRoute(message):
    # Check if the message is a private chat message
    if message['type'] == 'private':
        # Create a unique session ID for the user
        user_id = message['user_id']
        session_id = f"agent:private:{user_id}"
        return session_id
    else:
        # Default session ID for non-private messages
        return "agent:main:main"

Infra/Dependency Fixes:

• Ensure that the WeCom plugin version is compatible with the OpenClaw version.
• Verify that the dynamic agent creation mechanism is implemented for the WeCom channel.

Verification

To verify that the fix worked:

1. Send a private chat message from User A to the OpenClaw Agent.
2. Check if the message appears only in User A's conversation and not in User B's conversation.
3. Repeat the test with multiple users to ensure that each user's private chat messages are isolated and not visible to other users.

Extra Tips

• Regularly review and update the resolveAgentRoute function to ensure it handles different message types and scenarios correctly.
• Consider implementing the dynamic agent creation mechanism for the WeCom channel to improve scalability and performance.