Telegram code block escaping and formatting fixes
Cluster 2193 · gateway. Data as of
1 open item. Fix merged in #2200 on 20 Mar 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #2200. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #2200. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These items address a bug where backslashes and special characters are incorrectly stripped or escaped inside inline code and fenced code blocks in Telegram messages. Work spans both MarkdownV2 escaping fixes and a shift toward using Telegram's MessageEntity API as an alternative approach.
Open issues0
Open PRs1
- PR#11287feat(gateway): send Telegram messages via MessageEntity instead of MarkdownV2
Fixes on record
-
#2200 fix(telegram): escape backslashes and backticks inside code entities for Telegram (MarkdownV2)
files:
gateway/platforms/telegram.py,tests/gateway/test_telegram_format.py
Closed issues · 1
- Closed#2193[Bug]: Backslashes stripped inside inline code and fenced code blocks on Telegram
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- gateway
- Merged PRs
- #2200
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 20 Mar 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.