NousResearch/hermes-agent

In-place compaction commit and marker stamping fixes

Cluster 98450. Data as of

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

These items address bugs in the in-place compaction path where the persisted marker was not stamped after commit, causing transcript re-INSERTs, live-set token regrowth, and false triggering of local compression in native-Codex sessions.

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.

  • #98543 fix(compression): compacted native-Codex sessions no longer false-trigger 600s local compression mid-turn (#96995, #97602, salvage #97006)

    merged to main

    files: agent/conversation_loop.py, agent/turn_context.py, tests/agent/test_native_preflight_estimate.py

  • #98997 fix(compression): in-place compaction commits no longer re-INSERT the transcript (#98450)

    merged to main

    files: agent/context_compressor.py, agent/conversation_compression.py, tests/run_agent/test_in_place_persist_marker_98450.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #98458 fix(compression): stamp _DB_PERSISTED_MARKER after in-place batch commit · merged via another change → 1f2bd9e, #98997, #97006, #98543
Closed issues · 1
  • Closed#98450fix(compression): in-place compaction commit never stamps _DB_PERSISTED_MARKER — post-compaction transcript re-INSERTs, live set regrows ~58K → ~512K tokens
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

Merged PRs
#98543, #98997
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
31 Aug 2026

For your agent

The same facts, typed.