# NousResearch/hermes-agent · Telegram streamed final messages: delivery recovery and disappearing messages

## Open now

- Nothing open on GitHub.

Three members relate to Telegram message delivery: two fix-oriented titles concern final delivery after streaming issues (flood, preview possibly disappearing), and one asks whether deduplication is causing messages to disappear. The titles suggest a shared area, but they do not establish that the causes are the same.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #62476. Verify it addresses your case.
- **Recommended:** read PR #62476 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## 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_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: 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

- #58958: Telegram messages disappearing due to deduplication?

## Prior & competing PRs

- **#62476: fix(telegram): recover final delivery after stream flood**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/stream_consumer.py`, `plugins/platforms/telegram/adapter.py`, `tests/gateway/test_telegram_final_delivery.py`
- **#59864: fix(telegram): commit streamed final when preview may disappear**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `04898631cb72dbf84f5c066c3f87fc8c94df53a7`, `4aa499ff9f3fcc0c38ce61da46805a4dcc8f612e`, `#62476`

## Fix status

- Merged to main in PR #62476 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-07-11`.