Cairn
NousResearch/hermes-agent

Telegram Bot API 10.1 rich message handling

Cluster 63485 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These issues and pull requests address problems with receiving and processing inbound rich messages introduced in Telegram Bot API 10.1. Concerns include silent ignoring of top-level rich_message updates and handling or converting them to markdown.

Open issues1

  • Issue#63485fix(telegram): top-level inbound rich_message updates are silently ignored

Open PRs2

  • PR#63491fix(telegram): handle Telegram Bot API 10.1 Rich Messages
  • PR#94899fix(telegram): receive inbound rich messages as markdown (Bot API 10.1)
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.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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/63485.json
cluster/63485.md