Memory store routing misclassification in background review
Cluster 30220 · agent. Data as of
Nothing open on GitHub. Fix merged in #115985 on 19 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 #115985. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #115985. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where background self-improvement review incorrectly routes facts between memory, skill, and user stores (USER.md vs MEMORY.md), including fixes to ensure content is written to the correct store without duplication.
Open issues0
Open PRs0
Fixes on record
-
#115985 fix(review): background review routes facts to USER.md vs MEMORY.md and never writes one fact to two stores (#30220, salvage #30227)
files:
agent/background_review.py,tests/agent/test_review_prompt_class_first.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#30227 fix(self-improvement): correct memory/skill/user store routing in background review prompts (#30220) · merged via another change →
#115985
Closed issues · 1
- Closed#30220Background Self-Improvement Review misclassifies content between memory/skill/user stores
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
- #115985
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 Sep 2026