Cairn
NousResearch/hermes-agent

Unanswered user text lost during persist override

Cluster 124731. Data as of

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

These items address a bug where an unanswered user message is dropped or overwritten when a persist override rewrites or merges a user row. The work covers identifying the problem and fixing the agent to preserve that text through the override.

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.

  • #126615 Unanswered user text survives the next turn's persist override (#124731, salvage #124770)

    merged to main

    files: agent/agent_runtime_helpers.py, agent/message_metadata.py, agent/session_persistence.py, contributors/emails/[email protected], tests/acp_adapter/test_failed_turn_closure.py, tests/agent/test_merged_user_override.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #124770 fix(agent): preserve unanswered user text through persist override · superseded by another PR → #124770, #124731, #94500, #121837, #104454, #120862
  • #125077 fix(agent): keep the pre-merge prefix when the persist override rewrites a merged user row · done elsewhere → #125077, #124731, #124770
Closed issues · 1
  • Closed#124731Persist override overwrites a merged user row, dropping the earlier unanswered message from the live list
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
#126615
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
28 Sep 2026

For your agent

The same facts, typed.

cluster/124731.json
cluster/124731.md