NousResearch/hermes-agent

Telegram streaming preview truncation and reporting fix

Cluster 98552. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

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.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: partial fix 1 · superseded by another PR 1

  • #98583 fix(gateway): reconcile unrecorded streaming previews against visible prefix (#98552) · superseded by another PR → fd99812, #95382, #98552
  • #98720 fix(telegram): report the clipped stream preview instead of a bare success (#98552) · partial fix → #98552, #48648
Closed issues · 1
  • Closed#98552Telegram streaming finalize fails — message truncated well under 4096 chars, content_delivered=True false positive
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: 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

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.