openclaw - 💡(How to fix) Fix [Bug]: Telegram group chats are not ingested/responded to by OpenClaw bot, while direct messages work normally, with evidence of group-to-supergroup migration handling [1 comments, 2 participants]

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Telegram group chats are not ingested/responded to by OpenClaw bot, while direct messages work normally, with evidence of group-to-supergroup migration handling

Steps to reproduce

1. Configure Telegram bot in OpenClaw

2. Verify direct messages with the bot work normally

3. Create a brand new plain Telegram group

4. Add at least one real human member

5. Add the bot to the group

6. Turn BotFather Group Privacy off

7. Make the bot an admin

8. Send fresh normal messages in the group

9. Restart the OpenClaw gateway

10. Check Telegram group response behavior and logs

Expected behavior

• Bot should receive and respond to Telegram group messages

• Group messages should be routed into OpenClaw normally

Actual behavior

• Direct Telegram chat works normally

• Bot does not respond in Telegram groups

• OpenClaw previously reported no discovered Telegram groups

• Fresh group test still produced no reply from bot

OpenClaw version

OpenClaw version: 2026.4.15

Operating system

macOS 15.7.5 (arm64)

Install method

npm

Model

openai-codex/gpt-5.4

Provider / routing chain

Telegram → OpenClaw local gateway → main agent session → openai-codex/gpt-5.4 via Codex OAuth

Additional provider/model setup details

What was tested

• Added bot to group

• Turned BotFather Group Privacy off

• Made bot admin

• Used a brand new plain test group

• Included a real human member

• Sent fresh messages after setup

• Restarted OpenClaw gateway

• Rechecked status after restart

OpenClaw-side evidence

• Telegram health probe = OK

• canJoinGroups = true

• canReadAllGroupMessages = true

• Config allows unmentioned group messages

• Telegram channel is running in polling mode

• Group directory previously returned no groups

• Channel audit showed:

• checkedGroups: 0

• groups: []

New log evidence from fresh group test

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

On sending a fresh message in the test group, OpenClaw logged:

• Group migrated: "Test" -5231648512 → -1003956572659

• No config found for old group ID -5231648512, migration logged only

Why this seems important

• This suggests Telegram group traffic is reaching the Telegram integration

• The failure may be related to group-to-supergroup migration / ID remapping

• Bot still does not reply after this migration event

Likely issue

This no longer looks like only a discovery/UI problem. It may be a runtime handling issue around Telegram migrated groups or supergroup ID remapping, even though direct Telegram messaging works correctly.

Extra notes

This does not appear to be a simple Telegram setup mistake at this point, because the same failure persisted after fresh group creation, privacy changes, admin promotion, fresh messages, and a gateway restart.