Memory context injection framing and contamination issues
Cluster 65891 · agent. Data as of
Nothing open on GitHub. Fix merged in #75921 on 1 Aug 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 #75921. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #75921. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs concern how recalled memory and skill context is injected into conversations — including problems with role assignment, message contamination, deduplication of markers, gateway isolation, and framing memory as background context rather than authoritative user content.
Open issues0
Open PRs0
Fixes on record
-
#75921 fix(gateway): dedup model-switch markers so they don't accumulate in history (fixes #65891)
files:
tests/tui_gateway/test_model_switch_marker_role.py,tui_gateway/server.py
2 PRs closed without merging
From the close comments: merged via another change 2
Closed issues · 1
- Closed#65891Model switch markers ([System: The active model...]) pollute conversation history and permanently waste context tokens with no cleanup
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
- Subsystem
- agent
- Merged PRs
- #75921
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 1 Aug 2026