Cairn
NousResearch/hermes-agent

Duplicate final messages after streaming edit failures (Slack, Telegram)

Cluster 25256 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 3 PRs 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.

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.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: partial fix 2 · done elsewhere 1

  • #25258 Fix duplicate Slack final replies after stream finalize failure · partial fix → bc42e62, #25256
  • #36975 fix(streaming): suppress duplicate final send when edit fails after content delivery · done elsewhere → 0489863, #36965
  • #38732 fix(gateway): prevent Telegram duplicate messages and tool-trace leakage (#36965 #37555) · partial fix → #36965, #37555
Closed issues · 2
  • Closed#25256Slack streamed replies can duplicate after transient final edit failure
  • Closed#36965[Bug]: Streaming edit transport duplicates final message when Telegram rate-limits the cursor-strip edit
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.34: 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
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/25256.json
cluster/25256.md