Cairn

Preflight compression skips sessions with few large messages

NousResearch/hermes-agent · cluster 27404 · agent

Data as of

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

The short answer

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

A bug where the preflight compression guard checks message count rather than token count, silently bypassing compression when sessions have few but very large messages that exceed the token threshold. Multiple fix attempts and duplicates are grouped here.

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.

  • #52114 fix(agent): trigger preflight compression on few-but-huge sessions (#27405)

    merged to main

    files: agent/turn_context.py, scripts/release.py, tests/agent/test_preflight_compression_gate.py

3 PRs closed without merging

From the close comments: done elsewhere 2 · merged via another change 1

  • #27424 fix(agent): trigger preflight compression on token threshold for few huge messages (#27405) · done elsewhere
  • #27435 fix(agent): trigger preflight compression on few-but-huge sessions · merged via another change → aacc6bb, #27405, #52114
  • #52058 fix(agent): trigger preflight compression on few-but-huge sessions (#27405) · done elsewhere → #52114, #27405
Closed issues · 2
  • Closed#27404[Bug] 预检压缩的消息数量守卫在 token 已超阈值时静默跳过
  • Closed#27405Preflight compression guard bypasses token threshold, causing silent context overflow on sessions with few messages but large total tokens
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.29: 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
#52114
Closed issues
2
Attempts
3 PRs closed without merging
Fix link checked
24 Jun 2026

For your agent

The same facts, typed.

cluster/27404.json
cluster/27404.md