openclaw - 💡(How to fix) Fix [Bug]: Telegram reply/quote context not passed to assistant — regression in 2026.4.27 (upgrade from 4.15) [1 comments, 2 participants]

TL;DR

The issue can likely be resolved by investigating changes in the Telegram message handling between OpenClaw versions 2026.4.15 and 2026.4.27, focusing on how reply contexts are processed.

Guidance

• Review the changelog and release notes for OpenClaw versions between 2026.4.15 and 2026.4.27 to identify any changes related to Telegram integration or message handling.
• Compare the message processing logic in both versions to pinpoint differences in how reply contexts are extracted and passed to the assistant.
• Investigate if the issue is related to the one described in #75190, considering the possibility of a common root cause affecting Telegram message handling.
• Test the behavior with different types of messages and quoting scenarios to understand the scope of the issue.

Example

No specific code example can be provided without access to OpenClaw's source code, but the investigation should focus on functions or methods responsible for handling Telegram message quotes and replies.

Notes

The solution may require updates to how OpenClaw handles Telegram's message quoting feature, potentially involving changes to the Telegram API interaction or the internal message processing logic.

Recommendation

Apply a workaround by downgrading to OpenClaw version 2026.4.15 until the root cause is identified and fixed in a future release, as this version is known to work correctly with the described functionality.