Cairn

Session history ordering and identity during pruning

NousResearch/hermes-agent · cluster 117750

Data as of

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

The short answer

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

These items address bugs where pruning and compaction of session history caused tool-bearing messages to appear duplicated or reordered, and where display identity was incorrectly tied to payload rather than call ID.

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.

  • #132131 Pruned tool results no longer reappear after later answers (#117750, salvage #131494)

    merged to main

    files: hermes_state_identity.py, hermes_state_messages.py, tests/hermes_state/test_display_dedupe_pruned_tool_payload.py

4 PRs closed without merging

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

  • #117766 fix(sessions): keep pruned history in its original display order · superseded by another PR → 73da8e6, #132131
  • #117770 fix(state): tool-bearing display identity follows the call id, not the payload · merged via another change → 73da8e6, #132131
  • #117824 fix(sessions): keep display identity across prune-shaped compaction carries · superseded by another PR → 73da8e6, #132131, #117766
  • #131494 fix(state): key display identity of tool rows on stable tool identity, not payload bytes (#117750) · merged via another change → 73da8e6, f50b615, #132131
Closed issues · 1
  • Closed#117750[Bug] Pruning carried-forward tool payloads duplicates and reorders display history
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.33: 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
#132131
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
3 Oct 2026

For your agent

The same facts, typed.

cluster/117750.json
cluster/117750.md