Stale close stamps blocking session compression fix
Cluster 106459. Data as of
Nothing open on GitHub. Fix merged in #107187 on 10 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 #107187. 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 issues and PRs concern a bug where a stale explicit-close timestamp on an active session causes compression to permanently no-op with no recovery path. The work addresses detecting and healing such stale end stamps so compression can proceed normally.
Open issues0
Open PRs0
Fixes on record
-
#107187 fix(sessions): a stale explicit-close stamp no longer wedges compression (#106459, salvage #106543)
files:
hermes_state_common.py,hermes_state_compression.py,tests/tui_gateway/test_106459_routing_provenance_reopen.py,tests/tui_gateway/test_bot_live_owner_delivery.py,tools/session_search_tool.py,tui_gateway/prompt_turn.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · other 1
Closed issues · 1
- Closed#106459Pain cluster: over-limit sessions become permanently uncompressible — compression result is discarded when the session row is marked ended, /compress no-ops, no recovery path
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
- #107187
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 10 Sep 2026