openclaw - 💡(How to fix) Fix Feature: Forward reply_to_message context in Telegram inbound metadata [1 participants]

Problem

When a user replies to a specific message in a Telegram chat, the OpenClaw agent does not receive the referenced message content. The Telegram Bot API provides reply_to_message in the update payload, but this information is not forwarded to the agent in the inbound metadata.

This means:

• Agents cannot understand what message the user is replying to
• Context from referenced messages is lost
• Users expect agents to understand reply context naturally (as they would in a normal chat)

Proposed Solution

Include reply_to_message content in the inbound metadata JSON that gets passed to the agent session. This could include:

• The text of the referenced message
• The message_id of the referenced message
• Media attachments info from the referenced message
• Sender info of the referenced message

This data is already available in the Telegram Bot API update payload - it just needs to be forwarded through the OpenClaw gateway to the agent.

Use Case

User sends a reply to an old message saying "what about this?" - the agent should be able to read the referenced message content to understand the context, rather than asking the user to repeat or copy-paste.

Additional Context

OpenClaw version: 2026.4.15 Channel: Telegram direct message Currently the inbound metadata only includes sender info, chat_id, and message_id, but not reply_to_message data.