Cairn
NousResearch/hermes-agent

Session search child/lineage content retrieval corrections

Cluster 6507 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
9items grouped
Known?
Yes. 9 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 7 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

Multiple corrections address a bug where session_search incorrectly retrieved content from a parent/root session instead of the FTS5-matched child or continuation session. The changes aim to preserve child-hit recall and correct content routing in search results.

Open issues1

  • Issue#6507Bug: session_search drops child/continuation-session hits by summarizing only the lineage root

Open PRs0

No open pull requests.

7 PRs closed without merging

From the close comments: duplicate 3 · closed without comment 1 · done elsewhere 1 · superseded by another PR 1 · other 1

  • #6536 fix: improve session_search lineage recall · other → abf1af5, #27590
  • #20794 fix(session_search): load transcript from matched child session, not resolved root · closed without comment
  • #22233 fix(session_search): use original session ID for content retrieval · superseded by another PR → #22411, #22150
  • #22411 fix(session_search): route content retrieval to FTS5-matched child session · duplicate → #22233, #22150
  • #22538 fix(session_search): retrieve content from FTS5 child, not resolved parent · duplicate → #22411, #22150, #22538, #15909
Show 2 more
  • #22621 fix(session_search): use original session ID for content retrieval · duplicate → #22411, #22150, #22233, #22538
  • #23561 fix(session-search): read content from matched session · done elsewhere → abf1af5, #22150, #6507
Closed issues · 1
  • Closed#22150fix(session_search): use original session ID for content retrieval
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.20: 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
agent
Closed issues
1
Attempts
7 PRs closed without merging

For your agent

The same facts, typed.

cluster/6507.json
cluster/6507.md