NousResearch/hermes-agent

Native compaction threshold not following local trigger setting

Cluster 88695 · agent. Data as of

Nothing open on GitHub. Fix merged in #98542 on 30 Aug 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 #98542. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #98542. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items concern a bug where the native response compaction threshold defaults to 200K instead of deriving from the locally configured trigger value. Two fixes address how the native threshold is calculated or unset relative to the local trigger.

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.

  • #98542 fix(compression): native Codex compaction no longer fires at the stale 200K default on 900K windows (#88695, salvage #88722)

    merged to main

    files: agent/agent_init.py, agent/native_compaction.py, cli-config.yaml.example, hermes_cli/config_defaults.py, tests/run_agent/test_native_compaction.py, website/docs/developer-guide/context-compression-and-caching.md

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #88717 fix(compaction): unset native threshold follows the local trigger · superseded by another PR → #88722, #88695
  • #88722 fix(compression): derive native threshold from local trigger · merged via another change → #98542
Closed issues · 1
  • Closed#88695[Bug]: Native Responses compaction still fires at the 200K default while the Codex OAuth window is now 900K
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
#98542
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
30 Aug 2026

For your agent

The same facts, typed.