Bug Description
When receiving messages from a Telegram group, replies are being sent to the user's direct message (DM) chat_id instead of the group chat_id where the message originated.
Steps to Reproduce
- Set up a Telegram bot with group messaging enabled
- Add bot to a Telegram group
- Send a message in the group
- Bot receives the message and creates a session for the group correctly
- Bot typing indicator shows in the group
- But the reply is sent to the user's DM instead of the group
Expected Behavior
Replies should be sent back to the same group where the message was received.
Actual Behavior
Replies are sent to the user's direct message chat_id (e.g., 6543104235) instead of the group chat_id (e.g., -5167418353).
Evidence
Log shows: telegram sendMessage ok chat=6543104235 message=4531
Expected: telegram sendMessage ok chat=-5167418353 message=4531
The session IS correctly created for the group (agent:main:telegram:group:-5167418353), but outbound messages route to the wrong target.
Environment
- OpenClaw Version: 2026.5.7 (eeef486)
- Platform: Heyron.ai hosted gateway
- Telegram Plugin
Workarounds
Direct messages (DM) work correctly. Only group messaging is affected.
Bug Description
When receiving messages from a Telegram group, replies are being sent to the user's direct message (DM) chat_id instead of the group chat_id where the message originated.
Steps to Reproduce
Expected Behavior
Replies should be sent back to the same group where the message was received.
Actual Behavior
Replies are sent to the user's direct message chat_id (e.g., 6543104235) instead of the group chat_id (e.g., -5167418353).
Evidence
Log shows:
telegram sendMessage ok chat=6543104235 message=4531Expected:
telegram sendMessage ok chat=-5167418353 message=4531The session IS correctly created for the group (agent:main:telegram:group:-5167418353), but outbound messages route to the wrong target.
Environment
Workarounds
Direct messages (DM) work correctly. Only group messaging is affected.