NousResearch/hermes-agent

Agent session row deletion causes silent message loss

Cluster 123583. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #124117 on 26 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #124117, then check it covers your case.

Read #124117 Pick up a Lab task

A bug where deleting a session row while an agent is active causes all subsequent turns to be silently dropped due to a foreign key constraint failure, along with a fix that recreates the missing session row instead of dropping messages.

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.

#124117 fix(agent): a chat whose session row was deleted recreates it instead of dropping every later turn

merged to main

files: agent/session_persistence.py, agent/turn_explainers.py, hermes_state_errors.py, hermes_state_user_copy.py, tests/agent/test_session_row_under_live_agent_persist.py, website/docs/user-guide/sessions.md, website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/sessions.md

1 PR closed without merging

From the close comments: done elsewhere 1

#123641 fix(agent): heal a session row deleted under a live agent (#123583) · done elsewhere → 819c624, #124117

Closed issues · 1

Closed#123583[Bug]: a session row removed from the store under a live agent silently drops every later turn's messages — append_message FOREIGN KEY constraint failed, no retry, no trace

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.67: 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: #124117
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 26 Sep 2026

For your agent

The same facts, typed.

cluster/123583.json
cluster/123583.md