Rotation compression _db_persisted marker bug fixes
Cluster 57491. Data as of
Nothing open on GitHub. Fix merged in #57574 on 3 Jul 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 #57574. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #57574. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests address a bug where the _db_persisted marker is incorrectly copied during rotation compression assembly, causing bulk flush to child sessions to be skipped. The work involves stripping or correcting that marker to ensure proper persistence of rotated compression transcripts.
Open issues0
Open PRs0
Fixes on record
-
#57574 fix(agent): strip _db_persisted on rotation compression assembly (salvage #57531, #57491)
files:
agent/context_compressor.py,tests/agent/test_context_compressor.py,tests/run_agent/test_compression_persistence.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#57491Rotation compression: _db_persisted marker copied via messages[i].copy() skips bulk flush to child session (cached gateway regression since #50372)
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
- #57574
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 3 Jul 2026