NousResearch/hermes-agent

Persist compression failure cooldown across restarts

Cluster 74136 · gateway. Data as of

Nothing open on GitHub. Fix merged in #75884 on 1 Aug 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #75884. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #75884. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs address a bug where the session hygiene compression failure cooldown was stored only in memory, causing the same failing compression to re-trigger after restarts. The work involves persisting the cooldown state to a database so it survives process restarts.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #75884 fix(compression): index clamps, persisted failure cooldown, user-query preservation, thinking-token estimates

    merged to main

    files: agent/context_compressor.py, agent/model_metadata.py, contributors/emails/[redacted:email], gateway/run.py, tests/agent/test_budget_reasoning_details_exclusion.py, tests/agent/test_compressor_tail_cut_oob_fix.py, tests/agent/test_compressor_zero_user_guard.py, tests/gateway/test_session_hygiene.py

2 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1

  • #74251 fix: persist session hygiene compression cooldown to state DB · merged via another change → #75884, #74136
  • #74417 fix(gateway): persist session hygiene compression-failure cooldown to state DB (#74136) · duplicate → #74251, #74136
Closed issues · 1
  • Closed#74136[Bug]: Session hygiene compression cooldown is in-memory only — restarts re-trigger the same failing compression, wedging session storage
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.00 means 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

At a glance

Subsystem
gateway
Merged PRs
#75884
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
1 Aug 2026

For your agent

The same facts, typed.