Telegram tool-progress repeat counter breaking code fences
Cluster 138148 · gateway. Data as of
Nothing open on GitHub. Fix merged in #139710 on 16 Oct 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 #139710. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #139710. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items all concern the repeated tool-progress counter interfering with the closing code fence in Telegram messages, which causes backticks to render escaped or literal. The members include an issue report and fix-oriented pull requests (one referencing #138148 and #138150), but the titles alone don't confirm the outcome.
Open issues0
Open PRs0
Fixes on record
-
#139710 Repeated tool-progress lines no longer break code blocks on Telegram (#138148, salvage #138150)
files:
gateway/run_turn_progress.py,tests/gateway/test_telegram_format.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#138151 fix(gateway): keep the tool-progress repeat counter off the closing code fence · done elsewhere →
#139710
Closed issues · 1
- Closed#138148Tool-progress repeat counter corrupts the Telegram code fence → backticks render escaped/literal
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
- #139710
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Oct 2026