Cairn
NousResearch/hermes-agent

Telegram Bot API 9.5 sendMessageDraft support

Cluster 4014 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

Multiple proposals and implementations for adding support for the sendMessageDraft method introduced in Telegram Bot API 9.5, including streaming reply functionality. These appear to be overlapping or iterative attempts at the same feature.

Open issues0

No open issues.

Open PRs0

No open pull requests.

1 PR closed without merging

From the close comments: other 1

  • #4022 feat(telegram): add send_draft() using Bot API 9.5 sendMessageDraft · other
Closed issues · 2
  • Closed#4014feat(telegram): support sendMessageDraft method from Bot API 9.5
  • Closed#21439feat(telegram): streaming reply via sendMessageDraft (Bot API 9.5+)
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.45: 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
2
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/4014.json
cluster/4014.md