# NousResearch/hermes-agent · Duplicate final messages after streaming edit failures (Slack, Telegram)

## Open now

- Nothing open on GitHub.

Most members concern duplicate final replies in streamed messaging output when a final edit or finalize step fails or is rate-limited, with Slack and Telegram examples. One Telegram-focused member also mentions tool-trace leakage, which goes beyond the shared duplicate-message theme.

## TL;DR

- 5 member(s): 0 open issue(s), 2 closed issue(s), 0 open PR(s), 0 merged PR(s), 3 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.34`: 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

- #25256: Slack streamed replies can duplicate after transient final edit failure
- #36965: \[Bug\]: Streaming edit transport duplicates final message when Telegram rate-limits the cursor-strip edit

## Prior & competing PRs

- **#25258: Fix duplicate Slack final replies after stream finalize failure**. closed without merge · fix tier `suggested`
  - maintainer direction: category `partial_fix`; implication `needs_llm`; refs `bc42e62b171c622eab9dc9c2d9860e24feb1fe9f`, `#25256`
- **#38732: fix(gateway): prevent Telegram duplicate messages and tool-trace leakage (#36965 #37555)**. closed without merge · fix tier `suggested`
  - maintainer direction: category `partial_fix`; implication `needs_llm`; refs `#36965`, `#37555`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#36975: fix(streaming): suppress duplicate final send when edit fails after content delivery**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `04898631cb72dbf84f5c066c3f87fc8c94df53a7`, `#36965`

## Fix status

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