# NousResearch/hermes-agent · Gateway startup sweep incorrectly prunes recovered session routes

## Open now

- Nothing open on GitHub.

These items address a bug where the gateway's startup recovery process removes sessions.json entries or routes even when session recovery succeeds with the same session ID. The fix ensures that only routes with a different session ID trigger repointing or pruning.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #96428. Verify it addresses your case.
- **Recommended:** read PR #96428 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-96428`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #95957: Gateway startup sweep prunes routes whose session recovery SUCCEEDED — repoint branch only fires on a different session id

## Prior & competing PRs

- **#96428: fix(gateway): keep sessions.json route when startup recovery succeeds with the same session id (salvage #95963)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/session.py`, `tests/gateway/test_session_store_stale_prune.py`
- **#95963: fix(gateway): keep sessions.json entry when startup recovery succeeds with same session id**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#96428`

## Fix status

- Merged to main in PR #96428 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-08-27`.