# NousResearch/hermes-agent · Session search missing current lineage recall hits

## Open now

- Nothing open on GitHub.

These items address a bug where session search fails to surface hits from the current session's own /new-reset lineage. The fix targets gateway recall going blind to that specific set of sessions.

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

- #85756: session_search discovery hides ALL hits from the current session's own /new-reset lineage (gateway recall goes blind)

## Prior & competing PRs

- **#86652: fix(session-search): recall /new-reset sessions in the current lineage (#85756)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `tests/tools/test_session_search.py`, `tools/session_search_tool.py`
- **#85764: fix(session-search): recall /new-reset sessions in the current lineage (#85756)**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#86652`

## Fix status

- Merged to main in PR #86652 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-08-15`.
- Subsystem: `agent`