# NousResearch/hermes-agent · Telegram streaming preview truncation and reporting fix

## Open now

- Nothing open on GitHub.

These items concern a bug where Telegram streaming messages were being truncated and incorrectly reported as successfully delivered. The work addresses reconciling unrecorded streaming previews and fixing the gateway to report the actual clipped content rather than a false positive success.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 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_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

- #98552: Telegram streaming finalize fails — message truncated well under 4096 chars, content_delivered=True false positive

## Prior & competing PRs

- **#98583: fix(gateway): reconcile unrecorded streaming previews against visible prefix (#98552)**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `fd998120c1`, `#95382`, `#98552`
- **#98720: fix(telegram): report the clipped stream preview instead of a bare success (#98552)**. closed without merge
  - maintainer direction: category `partial_fix`; implication `needs_llm`; refs `#98552`, `#48648`

## Fix status

- No merged fix on record.