Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Telegram group chats are not discovered or ingested by OpenClaw bot, while direct messages work normally [4 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#74497•Fetched 2026-04-30 06:23:31
View on GitHub
Comments
4
Participants
3
Timeline
9
Reactions
2
Author
kabes1123kabes1123
Participants
clawsweeper[bot]clawsweeper[bot]jackyjhihjackyjhihkabes1123kabes1123
Timeline (top)
commented ×4labeled ×2closed ×1cross-referenced ×1

Telegram group chats are not discovered or ingested by OpenClaw bot, while direct messages work normally

Root Cause

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.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Telegram group chats are not discovered or ingested by OpenClaw bot, while direct messages work normally

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 discovery and response behavior

Expected behavior

• Bot should receive and respond to Telegram group messages

• OpenClaw should discover Telegram groups

• openclaw directory groups list --channel telegram should show the group

Actual behavior

• Direct Telegram chat works normally

• Bot does not respond in Telegram groups

• OpenClaw does not discover any Telegram groups

• openclaw directory groups list --channel telegram returns No groups found

OpenClaw version

OpenClaw version: 2026.4.15

Operating system

OS: macOS 15.7.5 (arm64)

Install method

npm

Model

openat-codex/gpt-5.4provi

Provider / routing chain

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

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

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 still returns no groups

• Channel audit shows:

• checkedGroups: 0

• groups: []

New log evidence from fresh group test

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.

extent analysis

TL;DR

The issue may be related to Telegram group-to-supergroup migration or ID remapping, causing OpenClaw to fail in discovering and responding to group messages.

Guidance

  • Investigate the group ID remapping logic in OpenClaw to ensure it correctly handles Telegram's group-to-supergroup migration.
  • Verify that the canReadAllGroupMessages and canJoinGroups permissions are correctly set and propagated after the group migration.
  • Check the OpenClaw logs for any errors or warnings related to group ID migration or supergroup handling.
  • Test the OpenClaw setup with a different Telegram group to see if the issue is specific to the current group or a more general problem.

Example

No code snippet is provided as the issue seems to be related to the internal logic of OpenClaw and Telegram integration, and not a specific code snippet.

Notes

The issue may not be related to the OpenClaw version or the operating system, as the problem persists after a fresh group creation and gateway restart. The fact that direct messages work correctly suggests that the issue is specific to group messages and the group-to-supergroup migration.

Recommendation

Apply a workaround by manually configuring the group ID in OpenClaw or updating the group ID remapping logic to correctly handle Telegram's group-to-supergroup migration, as the issue seems to be related to this specific functionality.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

• Bot should receive and respond to Telegram group messages

• OpenClaw should discover Telegram groups

• openclaw directory groups list --channel telegram should show the group

#dependency error#configuration error#environment variable#network issue#logging issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Telegram group chats are not discovered or ingested by OpenClaw bot, while direct messages work normally [4 comments, 3 participants]