NousResearch/hermes-agent

Session persistence error messaging and recovery fixes

Cluster 81227 · apps/desktop. Data as of 2026-10-29 11:48 UTC

Nothing open on GitHub. Fix merged in #81613 on 8 Aug 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 #81613. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #81613 Pick up a Lab task

These items address misleading or uninformative error messages when session persistence fails, including surfacing the real cause of failures and improving recovery messaging. A specific case of compression-lock contention causing silent session loss is also covered.

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.

#81613 fix: cause-aware session-persistence errors, gateway recovery message, doctor state.db stats (salvage #80693)

merged to main

files: agent/conversation_loop.py, agent/tool_executor.py, agent/turn_finalizer.py, cron/scheduler.py, gateway/run.py, hermes_cli/doctor.py, hermes_state.py, run_agent.py, tests/gateway/test_normalize_empty_agent_response.py, tests/run_agent/test_tool_call_incremental_persistence.py, tests/run_agent/test_turn_completion_explainer.py, tests/test_state_db_stats.py

1 PR closed without merging

From the close comments: superseded by another PR 1

#81248 fix(agent): name the real cause of session_persistence_failed · superseded by another PR → #81613, #80693

Closed issues · 1

Closed#81227Desktop: turns aborted with misleading 'session storage could not be written' (compression-lock contention, no retry); sessions appear to vanish after disconnects

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

Subsystem: apps/desktop
Merged PRs: #81613
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 8 Aug 2026

For your agent

The same facts, typed.

cluster/81227.json
cluster/81227.md