Description:
There is a sudden regression on Telegram Web. Up until yesterday, interactions and formatted text messages from an AI/OpenClaw bot were rendering flawlessly. Starting today, the exact same bot messages fail to display on the web interface, showing the error: "This message is currently not supported on Telegram Web. Try getdesktop.telegram.org".
The messages continue to display perfectly fine on the official mobile applications, proving that the bot's payload/API response is correct. This is an issue specific to a recent change or broken parser in the Telegram Web client.
Steps to reproduce:
Use Telegram Web on any desktop browser.Send a prompt to a bot that returns markdown or rich text (which worked perfectly 24 hours ago).The web client now fails to parse the response and displays the desktop fallback warning.
Expected behavior:
The web client should render the message as it did yesterday, maintaining parity with the mobile application's parsing capabilities.
Environment data:
Platform: Telegram Web (Regression observed across multiple desktop PCs today)
Steps to reproduce
Use Telegram Web on any desktop browser.Send a prompt to a bot that
returns markdown or rich text (which worked perfectly 24 hours ago).The
web client now fails to parse the response and displays the desktop
fallback warning.
A bot Rich Message containing only a table shows:
“This message is currently not supported on Telegram Web.”
master already includes Rich Message/table support in PR #669:
https://github.com/morethanwords/tweb/pull/669
Could the current WebK build be deployed?