# NousResearch/hermes-agent · Session reopen misclassifies branch lineage as reset

## Open now

- Nothing open on GitHub.

These items address a bug where reopening a parent session incorrectly overwrites or misclassifies branch-child lineage as reset-successor provenance. The fix preserves branch lineage during reopen operations.

## 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 #111381. Verify it addresses your case.
- **Recommended:** read PR #111381 (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-111381`. 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

- #110552: Reset lineage provenance can be misclassified after reopen_session() backfills _reset_from

## Prior & competing PRs

- **#111381: fix(sessions): reopening a parent no longer rewrites a /branch child as a reset successor (#110552, salvage #110559)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_state_sessions.py`, `tests/hermes_state/test_hermes_state.py`
- **#110559: fix(sessions): preserve branch lineage on reopen**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`

## Fix status

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