Cairn
NousResearch/hermes-agent

Telegram bold/blockquote conversion ordering bug

Cluster 90773 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

A bug where Telegram MarkdownV2 bold conversion runs before blockquote conversion, corrupting expandable blockquote markers starting with **>. Multiple fix attempts address protecting blockquote markers prior to bold conversion.

Open issues1

  • Issue#90773[Bug]: Telegram MarkdownV2 bold conversion runs before blockquote conversion, corrupting `**>` expandable blockquote marker

Open PRs1

  • PR#90781fix(telegram): protect **> blockquote marker before bold conversion

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #90828 fix(telegram): preserve expandable quote markers before bold conversion · superseded by another PR → #90781
  • #91485 fix(gateway): protect blockquotes before bold conversion in telegram adapter · superseded by another PR → 9cd9374, e866412, #90781, #91485
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.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Subsystem
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/90773.json
cluster/90773.md