Skip to content

Bot replies in private Threaded Mode do not show reply header on Desktop #30881

Description

@llblab

Steps to reproduce

  1. Open a private chat with a bot that has BotFather Threaded Mode / Topics enabled.
  2. Send a user message inside one of the bot chat threads.
  3. From the bot, call Bot API sendMessage with:
{
  "chat_id": <private_chat_id>,
  "message_thread_id": <thread_id>,
  "text": "Bot reply text",
  "reply_parameters": {
    "message_id": <user_message_id>,
    "allow_sending_without_reply": true
  }
}

The reply_parameters.message_id points to a message in the same private bot chat/thread.

Expected behaviour

Telegram Desktop should display the message as a visual reply to the original message, the same way Telegram mobile clients do.

Actual behaviour

Telegram Desktop shows the bot message in the correct thread, but does not render the visual reply header/quote.

Telegram mobile clients render the same bot message correctly as a reply.

Notes

This appears specific to Telegram Desktop's rendering of replies in private bot Threaded Mode. The Bot API payload is accepted and routed to the correct thread, and mobile Telegram displays the reply header for the same message.

Observed working payload shape:

{
  "method": "sendMessage",
  "chat_id": 840585,
  "message_thread_id": 518877,
  "reply_parameters": {
    "message_id": 21059,
    "allow_sending_without_reply": true
  },
  "text": "..."
}

The same scenario was tested with both text-origin and voice-origin user messages; the Desktop UI did not show the visual reply header in either case, while mobile did.

Configuration

Operating system: Linux

Version of Telegram Desktop: unknown / current installed version

Installation source: unknown

Used theme: default/unspecified

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions