Session search metadata source reporting correction
Cluster 15909 · agent. Data as of
Nothing open on GitHub. Fix merged in #19732 on 4 May 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #19732. 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
- Nothing open on GitHub.
A bug was identified where session_search incorrectly reported platform/source metadata from FTS5 child sessions rather than the parent sessions. Related pull requests address this by changing the source to be read from the parent session.
Open issues0
Open PRs0
Fixes on record
-
#19732 fix(session-search): report source from resolved parent, not FTS5 child session
files:
tests/tools/test_session_search.py,tools/session_search_tool.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#15917 fix(session-search): report source from resolved parent, not FTS5 child session (#15909) · merged via another change →
#19732
Closed issues · 1
- Closed#15909[Bug]: session_search misreports platform/source metadata in session summaries
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.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- agent
- Merged PRs
- #19732
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 4 May 2026