kn8-codes 6183e8ce1b fix(telegram): make Bot API 10.1 rich messages opt-in (default off) ... Rich messages are not ready for primetime: current Telegram clients can render Bot API 10.1 rich messages as blank/unsupported bubbles and make them hard to copy as plain text, which is worse than the legacy MarkdownV2 path for command snippets and mobile handoffs. Default the rich_messages toggle to False so replies stay on the copyable legacy path; users opt in per bot via platforms.telegram.extra.rich_messages: true. Updates adapter, gateway config default, example config, English + zh-Hans docs, and the default/opt-in tests.		2026-06-21 12:03:24 -07:00
..
developer-guide	docs: align contributor test checklist with wrapper	2026-06-20 23:23:47 -07:00
getting-started	fix(docs): document curl, xz-utils, and g++ as Linux prerequisites	2026-06-20 23:23:47 -07:00
guides	docs: sync documentation with current implementation	2026-06-20 23:23:47 -07:00
integrations	docs(providers): clarify vllm qwen reasoning output	2026-06-20 23:23:47 -07:00
reference	fix(docs): align slash-command and docker docs	2026-06-20 23:23:47 -07:00
user-guide	fix(telegram): make Bot API 10.1 rich messages opt-in (default off)	2026-06-21 12:03:24 -07:00
index.mdx	docs: point desktop download links to site root (deprecate /desktop) (#46795)	2026-06-15 15:02:24 -04:00
user-stories.mdx	docs(website): add User Stories and Use Cases collage page (#18282)	2026-04-30 23:56:59 -07:00