NousResearch/hermes-agent

Silent session loss on unreadable transcript files

Cluster 100788. Data as of 2026-10-24 04:06 UTC

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

open issues

open PRs

items grouped

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

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

Read #100910 Pick up a Lab task

These items address a bug where a corrupt or unreadable state.db causes transcript loading to silently return empty, allowing a failed session to resume as a new conversation without any error signal. The fixes aim to distinguish a failing read from genuinely empty history.

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.

#100910 fix(gateway): unreadable state.db transcript no longer resumes as a new conversation (#100788, salvage #100798)

merged to main

files: gateway/run.py, gateway/session.py, tests/gateway/test_42039_duplicate_user_message.py, tests/gateway/test_session_continuity_82616.py

2 PRs closed without merging

From the close comments: merged via another change 1 · partial fix 1

#100798 fix(gateway): stop unreadable sessions from silently losing context · merged via another change → 2d37a3a, #100910
#100887 fix(gateway): distinguish failed transcript reads from empty history · partial fix → #101738, #100910

Closed issues · 1

Closed#100788[Bug]: load_transcript() returns [] on a failed read — a corrupt state.db silently resumes as a new conversation (gap in #82616)

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: #100910
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 2 Sep 2026

For your agent

The same facts, typed.

cluster/100788.json
cluster/100788.md