Issue: Telegram DMs not reaching OpenClaw (outbound OK)
- I’m running OpenClaw 2026.2.19-2 on Linux with the Telegram channel enabled.
- The bot is @HowardNeal_Bot. The token is valid (getMe works), and there is no
webhook set (getWebhookInfo shows empty URL).
- OpenClaw status says Telegram is OK, and outgoing messages from OpenClaw to my
chat ID arrive in Telegram fine.
- However, when I DM the bot from Telegram, nothing ever shows up on the OpenClaw
side:
- No pairing entries when I use dmPolicy: "pairing" and send /start or /pair
(pairing list is always empty).
- No visible inbound messages when I use dmPolicy: "open" or dmPolicy:
"allowlist" with my numeric user id.
- The logs only show “starting provider” and “No pending telegram pairing
requests”, but never any actual message/update lines, even when I send very
distinctive texts to the bot.
So: outbound to Telegram works, Telegram health is OK, but no inbound DMs are
delivered to OpenClaw at all, regardless of dmPolicy.
Ask: Is there anything obvious I’m missing, or a known bug in this version where
Telegram long polling doesn’t surface DMs to the gateway/agent loop even though
health checks pass? Happy to run specific debug commands or enable a Telegram
diagnostics flag if you tell me which.
- The bot is @HowardNeal_Bot. The token is valid (getMe works), and there is no
webhook set (getWebhookInfo shows empty URL).
- OpenClaw status says Telegram is OK, and outgoing messages from OpenClaw to my
chat ID arrive in Telegram fine.
- However, when I DM the bot from Telegram, nothing ever shows up on the OpenClaw
side:
- No pairing entries when I use dmPolicy: "pairing" and send /start or /pair
(pairing list is always empty).
- No visible inbound messages when I use dmPolicy: "open" or dmPolicy:
"allowlist" with my numeric user id.
- The logs only show “starting provider” and “No pending telegram pairing
requests”, but never any actual message/update lines, even when I send very
distinctive texts to the bot.
So: outbound to Telegram works, Telegram health is OK, but no inbound DMs are
delivered to OpenClaw at all, regardless of dmPolicy.
Ask: Is there anything obvious I’m missing, or a known bug in this version where
Telegram long polling doesn’t surface DMs to the gateway/agent loop even though
health checks pass? Happy to run specific debug commands or enable a Telegram
diagnostics flag if you tell me which.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Similar Threads
Was this page helpful?
