# NousResearch/hermes-agent · Telegram Bot API 9.5 sendMessageDraft support

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 2 closed issue(s), 0 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): 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 member 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.

## Closed / duplicate issues

- #4014: feat(telegram): support sendMessageDraft method from Bot API 9.5
- #21439: feat(telegram): streaming reply via sendMessageDraft (Bot API 9.5+)

## Prior & competing PRs

- **#4022: feat(telegram): add send_draft() using Bot API 9.5 sendMessageDraft**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`