Cairn

Compaction notice ignores progress_notices=false setting

NousResearch/hermes-agent · cluster 77549 · gateway

Data as of

Nothing open on GitHub. Fix merged in #96127. Check it covers your case.

The short answer

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

A bug where the compaction completion notice is sent regardless of the progress_notices=false configuration. Multiple fix attempts address gating or suppressing the notice when progress_notices is disabled.

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.

  • #96127 fix(compression): suppress duplicate compaction-complete notices (salvage of #71488)

    merged to main

    files: agent/conversation_compression.py, gateway/run.py, tests/agent/test_compression_concurrent_fork.py, tests/gateway/test_compression_progress_notices.py, tests/run_agent/test_413_compression.py, tests/run_agent/test_codex_app_server_compaction.py

4 PRs closed without merging

From the close comments: done elsewhere 3 · duplicate 1

  • #77551 fix(gateway): gate compaction completion notice · done elsewhere → #96127, #71488, #77549
  • #77563 fix(gateway): gate compaction completion notice under compression.progress_notices · done elsewhere → #96127, #71488, #77549
  • #77758 fix(gateway): suppress compaction completion notice when progress_notices=false · duplicate → #77551
  • #77841 fix(gateway): compaction completion notice respects progress_notices=false (closes #77549) · done elsewhere → #96127, #71488, #77549
Closed issues · 1
  • Closed#77549[Bug]: compaction completion notice ignores progress_notices=false
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.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
#96127
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
27 Aug 2026

For your agent

The same facts, typed.

cluster/77549.json
cluster/77549.md