Todo/policy state bugs during compression compaction
NousResearch/hermes-agent · cluster 84718 · agent
Data as of
Nothing open on GitHub. Fix merged in #85962. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #85962. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern bugs where compaction incorrectly handles todo items and policy state, including stale todos persisting beyond their policy and todos being re-injected without revalidation. The focus is on correctness of todo and policy lifecycle during compression.
Open issues0
Open PRs0
Fixes on record
-
#85962 fix(compaction): gate checkpoint replay/prune on current request eligibility (salvage #85919)
files:
agent/auxiliary_client.py,agent/codex_responses_adapter.py,agent/transports/codex.py,tests/run_agent/test_native_compaction.py -
#86852 fix(compression): couple pruned-skill reload instruction to the preserved todo snapshot
files:
agent/conversation_compression.py,tests/agent/test_skill_todo_retention_parity.py
4 PRs closed without merging
From the close comments: done elsewhere 2 · stale or abandoned 1 · superseded by another PR 1
-
#84808 fix(compression): stop stale todos from outliving their policy · stale or abandoned →
#84718 -
#85878 fix(compression): require todo revalidation after compaction · done elsewhere →
#85919,#85962,#84718 -
#86267 fix(compression): reframe preserved todos as planning context · superseded by another PR →
#87090,#86852 - #87090 fix(compression): close the compaction retention asymmetry completely (skills, todos, provenance, telemetry, anchor) - #84718 · done elsewhere
Closed issues · 1
- Closed#84718Compaction keeps the imperative and drops the policy: skills pruned mid-task while todos are re-injected verbatim (v0.19.1, gpt-5.6-luna)
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.33: 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 Lab