Cairn
NousResearch/hermes-agent

TUI session recovery after gateway exit or respawn

Cluster 39013 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These items all concern the TUI losing or needing to restore a session around a gateway exit or respawn. Two are fix-titled changes referencing #39013 (auto-resume after respawn; resolving in-memory session UUID in session.resume), and one is a report of 'gateway exited' and 'session not found' after rapid successive messages. The titles alone don't establish whether the changes address the report.

Open issues1

  • Issue#39013TUI: "gateway exited" + "session not found" after rapid successive messages in same turn

Open PRs1

  • PR#39123fix(tui): auto-resume session after gateway respawn (#39013)

1 PR closed without merging

From the close comments: other 1

  • #39167 fix(tui): resolve in-memory session UUID in session.resume for crash recovery #39013 · other
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

Subsystem
gateway
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/39013.json
cluster/39013.md