NousResearch/hermes-agent

Session transcript re-write on resume bug fixes

Cluster 92231 · agent. Data as of

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

These members address a bug where resumed session transcripts lack a persistence marker, causing the full transcript to be rewritten on every turn flush. The fixes focus on stamping or preserving persistence state at load or baseline time to prevent redundant re-appending.

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.

  • #92539 fix: stamp _db_persisted at row load time so resumed transcripts never re-append (#92231)

    merged to main

    files: agent/conversation_compression.py, agent/turn_finalizer.py, hermes_state.py, run_agent.py, tests/acp/test_session.py, tests/agent/test_load_time_durability_stamp_92231.py, tests/agent/test_session_rotation_flush_cold_resume_68454.py, tests/test_message_reactions.py

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #92269 fix(session): avoid rewriting resumed transcript on turn flush · superseded by another PR → #92231, #92539
  • #92272 fix(Session): preserve turn baseline for direct persistence recovery · superseded by another PR → #68196, #88551, #92539
Closed issues · 1
  • Closed#92231compression: turn flush re-writes entire transcript every turn (no _DB_PERSISTED_MARKER on resumed messages) — amplifies with adoption into exponential growth
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
#92539
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
23 Aug 2026

For your agent

The same facts, typed.