NousResearch/hermes-agent

Gateway session recovery and reset-boundary handling

Cluster 68539 · gateway. Data as of

2 open items. Fix merged in #82743 on 9 Aug 2026. Check it covers your case.

The short answer

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

Most members concern gateway session recovery respecting reset boundaries and idle time, with one issue describing older sessions being brought back after a session reset. One member covers making session identity durable across crashes and restarts, a related but somewhat different angle.

Open issues1

  • Issue#68539Gateway session recovery resurrects ancient never-ended sessions after session_reset — nightly reset silently undone, stale context resurfaces

Open PRs1

  • PR#68795fix(gateway): respect reset boundaries during session recovery (#68539)

Fixes on record

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

  • #82633 fix(gateway): make session identity durable so chat continuity survives crashes and restarts

    merged to main

    files: gateway/session.py, hermes_state.py, tests/gateway/test_session_continuity_82616.py

  • #82743 fix(gateway): session recovery honors reset boundaries and real idle time (#68617 + #78618 salvage)

    merged to main

    files: contributors/emails/[redacted:email], gateway/session.py, hermes_state.py, tests/gateway/test_session_store_runtime_stale_guard.py, tests/gateway/test_session_store_stale_prune.py, tests/test_hermes_state.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #68617 fix(gateway): respect reset boundaries during recovery (#68539) · merged via another change → #82743, #82633
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.40: 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
Merged PRs
#82633, #82743
Closed issues
0
Attempts
1 PR closed without merging
Fix link checked
9 Aug 2026

For your agent

The same facts, typed.