Cap per-message content in session search read shape
Cluster 114344. Data as of
Nothing open on GitHub. Fix merged in #114901 on 18 Sep 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 #114901. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #114901. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where the session search read shape returns uncapped message content, unlike FTS hits. The work involves applying a content length cap to per-message results in the read shape path.
Open issues0
Open PRs0
Fixes on record
-
#114901 fix(session_search): read shape and title-match entries cap per-message content like FTS hits (#114344, salvage #114349)
files:
contributors/emails/[redacted:email],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
-
#114349 fix(session_search): cap per-message content on the read shape · merged via another change →
77da057,#114901,#114344,#114349
Closed issues · 1
- Closed#114344session_search read shape returns uncapped message content (missed by #69334)
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
- Merged PRs
- #114901
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 18 Sep 2026