NousResearch/hermes-agent

Fix compression retry logic for would-grow rejections

Cluster 88568 · evals/compaction. Data as of 2026-10-29 11:48 UTC

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

open issues

open PRs

items grouped

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

Next step: read #90562, then check it covers your case.

Read #90562 Pick up a Lab task

These members address a bug where compression retries incorrectly reuse an unchanged transcript after a would-grow rejection. The fixes ensure would-grow refusals count as ineffective strikes and introduce a salvage pass for grown candidates.

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.

#90562 fix(compression): would-grow refusals strike the breaker; grown candidates get one salvage pass

merged to main

files: agent/context_compressor.py, agent/conversation_compression.py, cli-config.yaml.example, hermes_cli/config_defaults.py, tests/agent/test_compaction_anti_thrash.py, tests/agent/test_salvage_grown_transcript.py, tests/hermes_cli/test_set_config_value.py, tests/run_agent/test_in_place_compaction.py

1 PR closed without merging

From the close comments: merged via another change 1

#88593 fix(compression): count a would-grow refusal as an ineffective strike · merged via another change → #90562, #90353, #90354, #88568

Closed issues · 1

Closed#88568[Bug]: core compression retries unchanged transcript after would_grow rejection

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.67: 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: evals/compaction
Merged PRs: #90562
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 20 Aug 2026

For your agent

The same facts, typed.

cluster/88568.json
cluster/88568.md