You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Restore readable standard Telegram text delivery by default after Bot API 10.1 rich messages rendered as unsupported in current clients. Keep native rich tables and structured messages available through the account-level richMessages opt-in, with account-aware capability advertising and documented structural limits.
Fixes#93263.
Outbound text uses standard Telegram HTML messages by default so replies remain readable across current Telegram clients.
422
+
423
+
Set `channels.telegram.richMessages: true` to opt into Bot API 10.1 rich messages:
424
+
425
+
```json5
426
+
{
427
+
channels: {
428
+
telegram: {
429
+
richMessages:true,
430
+
},
431
+
},
432
+
}
433
+
```
422
434
423
435
- Markdown text is rendered through OpenClaw's Markdown IR and sent as Telegram rich HTML.
424
436
- Explicit rich HTML payloads preserve supported Bot API 10.1 tags such as headings, tables, details, rich media, and formulas.
425
437
- Media captions still use Telegram HTML captions because rich messages do not replace captions.
426
438
427
439
This keeps model text away from Telegram Rich Markdown sigils, so currency like `$400-600K` is not parsed as math. Long rich text is split automatically across Telegram's rich text and rich block limits. Tables over Telegram's column limit are sent as code blocks.
428
440
441
+
Rich messages require compatible Telegram clients. Some current Desktop, Web, Android, and third-party clients display accepted rich messages as unsupported, so keep this option disabled unless every client used with the bot can render them.
442
+
429
443
Link previews are enabled by default. `channels.telegram.linkPreview: false` skips automatic entity detection for rich text.
0 commit comments