Gateway session ID persistence across resets/crashes
Cluster 12857 · gateway. Data as of
1 open item. Fix merged in #82633 on 9 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 6 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #82633. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #82633. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
A bug was identified where the gateway's auto-reset discards the parent session ID, breaking chat continuity. Multiple fixes address persisting the session ID and restoring the transcript after resets or crashes.
Open issues0
Open PRs1
- PR#13536fix(gateway): persist parent session ID on auto-reset
Fixes on record
-
#82633 fix(gateway): make session identity durable so chat continuity survives crashes and restarts
files:
gateway/session.py,hermes_state.py,tests/gateway/test_session_continuity_82616.py
3 PRs closed without merging
From the close comments: closed without comment 1 · other 2
Closed issues · 1
- Closed#12857[Bug]: Auto-reset in gateway discards context — parent session ID never stored
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.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- gateway
- Merged PRs
- #82633
- Closed issues
- 1
- Attempts
- 3 PRs closed without merging
- Fix link checked
- 9 Aug 2026