NousResearch/hermes-agent

TUI session write ordering and row placement fixes

Cluster 123545 · apps/desktop. Data as of

1 open item. Fix merged in #128282 on 30 Sep 2026. Check it covers your case.

The short answer

0open issues
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #128282. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #128282. That is separate from the fix event.
Still open
0 issues and 1 PR.

These items address a bug where a single user turn's data could be split across multiple sessions, along with related fixes for row queuing, compaction survival, and reap record rotation ordering in the TUI gateway.

Open issues0

No open issues.

Open PRs1

  • PR#123573fix(desktop): rotate unprocessed reap records ahead of survivors so deadline starvation cannot strand trailing orphans

Fixes on record

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

  • #128282 fix(tui_gateway): one turn's rows land in one session, and the queued row survives an in-place compaction

    merged to main

    files: agent/message_metadata.py, hermes_state_messages.py, tests/tui_gateway/test_queued_prompt_persistence.py, tests/tui_gateway/test_submit_row_session_target.py, tests/tui_gateway/test_tui_gateway_server.py, tui_gateway/methods_prompt.py, tui_gateway/methods_session.py, tui_gateway/prompt_turn.py, tui_gateway/server.py, tui_gateway/session_auto_continue.py, tui_gateway/session_workdir.py

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #123635 fix(tui_gateway): file off-turn session writes in the session the turn will use (#123545) · superseded by another PR → #128282
Closed issues · 1
  • Closed#123545[Bug]: Windows - one user message written into two sessions, tool rows split across them (repro for #119171)
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.50: 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
apps/desktop
Merged PRs
#128282
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
30 Sep 2026

For your agent

The same facts, typed.