Cairn
NousResearch/hermes-agent

tail message floor token budget overflow fixes

Cluster 108647 · agent. Data as of

1 open item. Fix merged in #115987 on 19 Sep 2026. Check it covers your case.

The short answer

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

Multiple fixes and a feature addressing a bug where the tail message floor in context compression could exceed the configured token budget without an upper bound. Changes include bounding the floor, adding configurability, and preventing it from overriding lean token limits.

Open issues0

No open issues.

Open PRs1

  • PR#60662feat(compression): configurable max_tail_message_floor

Fixes on record

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

  • #115987 fix(compression): the recent-message floor no longer pushes the protected tail past its token ceiling (#108647, salvage #108651)

    merged to main

    files: agent/context_compressor.py, tests/agent/test_context_compressor.py

5 PRs closed without merging

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

  • #108651 fix(agent): bound tail message floor by token budget · merged via another change → #115987
  • #108824 fix(compression): bound tail message floor by token budget · merged via another change → #108651, #115987
  • #109523 fix(compression): bound tail message floor by lean token budget (#108647) · duplicate → #108651, #108647, #108824
  • #113028 fix(compression): bound oversized protected tails · duplicate
  • #127330 fix(context-compressor): prevent tail message floor from overriding token budget · done elsewhere → fdbcdef, 31447bd, #108647
Closed issues · 1
  • Closed#108647[Bug]: Tail message floor overrides the lean token budget with no upper bound (6.3x observed)
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.25: 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
#115987
Closed issues
1
Attempts
5 PRs closed without merging
Fix link checked
19 Sep 2026

For your agent

The same facts, typed.

cluster/108647.json
cluster/108647.md