Cairn
NousResearch/hermes-agent

Telegram rich messages causing web compatibility issues

Cluster 45785 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue 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 0 PRs.

Telegram Web cannot render rich/formatted assistant replies, prompting a change to make rich message formatting opt-in rather than the default behavior.

Open issues1

  • Issue#46098[Bug]: Telegram Web showing "This message is not supported on the web version of Telegram"

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 2

  • #45933 Make Telegram rich replies opt-in · duplicate → 6183e8c, #50322, #48422
  • #46317 fix(telegram): make Bot API 10.1 rich messages opt-in (default off) · duplicate → 6183e8c, #50322, #48422
Closed issues · 1
  • Closed#45785[Bug]: Telegram Web cannot render sendRichMessage assistant replies
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.39: 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
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/45785.json
cluster/45785.md