Telegram plugin: quoted/reply messages lose reply_to context

Resolved 💬 2 comments Opened Jun 13, 2026 by 1999 Closed Jun 16, 2026

Feature request

When a Telegram user quotes a previous message (reply), the Telegram Bot API includes reply_to_message in the update object. The current Telegram plugin drops this context when assembling the <channel> notification tag, so Claude cannot see which message is being quoted.

Impact

Claude receives <channel source="telegram" ...> with no indication that the message is a reply to a specific prior message, forcing it to ask for clarification or guess.

Proposed fix

Add reply_to_message_id to the meta object in the inbound channel notification:

// in external_plugins/telegram/server.ts, inside the meta object:
...(ctx.message?.reply_to_message?.message_id != null
  ? { reply_to_message_id: String(ctx.message.reply_to_message.message_id) }
  : {}),

And update the system prompt to mention the new attribute.

A PR with the exact change was opened but auto-closed because external contributions aren't accepted: https://github.com/anthropics/claude-plugins-official/pull/2760

The diff is 4 lines. Happy to provide more context if useful.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗