Cairn

History block duplication in state persistence layer

NousResearch/hermes-agent · cluster 129065 · agent

Data as of

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

The short answer

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

These items concern a bug where history blocks are duplicated in state storage during long sessions, and related fixes addressing how restored or re-flushed history blocks are identified and deduplicated by logical identity.

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.

  • #130632 fix(state): a re-flushed restored history block no longer duplicates in state.db (#129065, salvage #129133)

    merged to main

    files: agent/transcript_repair.py, hermes_state.py, hermes_state_common.py, hermes_state_messages.py, tests/acp_adapter/test_session.py, tests/hermes_state/test_unaddressed_rewrite_identity.py

3 PRs closed without merging

From the close comments: merged via another change 2 · closed without comment 1

  • #129110 fix(state): a re-flushed restored history block no longer duplicates · merged via another change → ac7927c, #130632
  • #129133 fix(state): recover unaddressed rewrites by logical identity · merged via another change → ac7927c, #130632
  • #130456 state: stamp reloaded dicts with persistence marker to prevent history duplication · closed without comment
Closed issues · 1
  • Closed#129065[Bug]: Desktop long sessions — a whole history block is duplicated in state.db (distinct message_uid, timestamps 21h apart), not renderer-only
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.40: 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
#130632
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
1 Oct 2026

For your agent

The same facts, typed.

cluster/129065.json
cluster/129065.md