openclaw - 💡(How to fix) Fix [Bug]: Telegram group mention replies are routed to user's DM instead of the group

Problem

When a user mentions the bot in a Telegram group, the agent receives the message correctly but the reply is sent as a Direct Message (DM) to the user instead of being posted back to the group chat.

Environment

• OpenClaw version: v2026.5.7 (eeef486)
• Channel: Telegram
• Chat type: Group (not forum topic)

Steps to Reproduce

1. Add the bot to a Telegram group
2. Configure group access with groupPolicy: "open" and requireMention: false
3. Mention the bot in the group (e.g., @BotName message)
4. Observe: the agent processes the message, but the reply lands in the user's DMs

Expected Behavior

The agent reply should be sent back to the same Telegram group chat where the mention occurred.

Actual Behavior

The reply is routed to the user's private DM with the bot instead of the group.

Configuration

{
  channels: {
    telegram: {
      enabled: true,
      dmPolicy: "allowlist",
      groupPolicy: "open",
      allowFrom: ["xxx"],
      groups: {
        "-100XXXXX": {
          groupPolicy: "open",
          requireMention: false
        }
      }
    }
  }
}

Additional Context

• The bot has admin/privacy mode disabled in Telegram
• Group message is received by the gateway (confirmed in logs)
• Agent processes the message correctly
• The delivery path seems to use user_id as the target instead of group_chat_id
• This appears to be a reply routing/delivery bug, not a mention processing bug
• Related to the same-chat message delivery changes in v2026.5.7 (Changelog: "Telegram: treat successful same-chat message tool outbound sends during an inbound Telegram turn as delivered...")