Cairn
NousResearch/hermes-agent

Warn users when context compression is blocked or running

Cluster 62708 · agent. Data as of

Nothing open on GitHub. Fix merged in #69857 on 23 Jul 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 #69857. 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 center on missing user feedback around context compression: no warning when context exceeds the compression threshold but compression is blocked (e.g., by cooldown or anti-thrash), and no in-progress indicator while /compress runs. One member is a fix proposing a warning for the blocked case; the others describe the requested behavior.

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.

  • #69857 fix(compression): warn the user when compression is blocked but context keeps growing

    merged to main

    files: agent/context_compressor.py, agent/context_engine.py, agent/conversation_compression.py, agent/conversation_loop.py, agent/turn_context.py, contributors/emails/stanislav@local, run_agent.py, tests/agent/test_turn_context.py, tests/agent/test_turn_context_overflow_warning.py, tests/gateway/test_telegram_noise_filter.py

2 PRs closed without merging

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

  • #62625 Surface warning when context exceeds compression threshold but compression is blocked · merged via another change → 01b0451, #69857
  • #62626 Show in-progress indicator while /compress runs · other
Closed issues · 1
  • Closed#62708Silent context-overflow: no warning when compression is blocked (cooldown/anti-thrash) + no in-progress indicator
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
agent
Merged PRs
#69857
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
23 Jul 2026

For your agent

The same facts, typed.

cluster/62708.json
cluster/62708.md