Bound memory use in @-reference expansion reads
Cluster 116562. Data as of
Nothing open on GitHub. Fix merged in #116930 on 20 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #116930. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116930. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests address unbounded data reads occurring during @file, @folder, and @diff context reference expansion before any size limits are applied. The work focuses on making expansion memory-bounded earlier in the process.
Open issues0
Open PRs0
Fixes on record
-
#116930 fix(agent): @file/@folder/@diff expansion stays memory-bounded before the size gates (#116562, salvage #116563)
files:
agent/context_references.py,tests/agent/test_context_references.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#116562@file:/@folder:/@diff expansion reads unbounded data before any size gate
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.50: 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
- #116930
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 20 Sep 2026