Cairn
NousResearch/hermes-agent

Telegram Bot API 10.1 rich messages bugs and fixes

Cluster 45762 · gateway. Data as of

Nothing open on GitHub. No fix on record.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 3 issues already closed.
Fix event
No merged or attempted fix PR is on record for this cluster.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests concern the implementation of Telegram Bot API 10.1 rich messages, including making the feature opt-in, fixing oversized body text rendering, correcting email entity detection, and handling streamed preview edits.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Closed issues · 3
  • Closed#45762[Bug]: Telegram Rich Message body text renders oversized vs normal bot messages
  • Closed#45771Telegram Rich Message body text renders too large compared with normal messages
  • Closed#46047[Bug]: Telegram Rich Message body text renders oversized vs normal bot messages
How this cluster was grouped
  • Link evidence (automated judgement only): no structural link between members; the grouping rests entirely on an automated relevance judgement over their text.
  • Read the members yourself before treating them as one problem.
  • Pairwise link density 0.36: 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
3
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/45762.json
cluster/45762.md