Cairn

Streaming tail content lost at message completion

NousResearch/hermes-agent · cluster 61506 · dashboard

Data as of

Nothing open on GitHub. Fix merged in #121740. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #121740. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #121740. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and fixes address a bug where buffered or unflushed streaming text is wiped or dropped when a message.complete event arrives with a separate payload.text field. Fixes span both the desktop/ink and TUI interfaces.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #121740 fix(tui): keep the streamed tail at message.complete and render combining marks correctly

    merged to main

    files: ui-tui/packages/hermes-ink/src/ink/log-update.test.ts, ui-tui/packages/hermes-ink/src/ink/log-update.ts, ui-tui/packages/hermes-ink/src/ink/termio/parser.ts, ui-tui/src/__tests__/createGatewayEventHandler.test.ts, ui-tui/src/app/turnController.ts

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #61541 fix(ui-tui): preserve unflushed streaming tail when message.complete has separate payload.text · done elsewhere → c502cd0, #61520, #121740
  • #73611 fix(ui-tui): flush the buffered streaming tail at message.complete · merged via another change → c502cd0, #121740, #61520
Closed issues · 2
  • Closed#61506TUI: unflushed streaming tail lost on message.complete when payload.text is separate final text
  • Closed#61520TUI: unflushed streaming tail lost on message.complete when payload.text is separate final text
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
dashboard
Merged PRs
#121740
Closed issues
2
Attempts
2 PRs closed without merging
Fix link checked
24 Sep 2026

For your agent

The same facts, typed.

cluster/61506.json
cluster/61506.md