NousResearch/hermes-agent

Model switch history version mismatch bug fixes

Cluster 76870. Data as of

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

The short answer

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

A bug where switching models mid-session caused history_version mismatches, resulting in discarded agent output and empty assistant messages. Fixes address snapshotting history and merging agent output when this mismatch occurs.

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.

  • #77324 fix(tui): snapshot history after pending model switch applies (#76870)

    merged to main

    files: relatorio-issue-69678-sqlite-fd-leaks.md, tests/test_tui_gateway_server.py, tui_gateway/server.py

  • #77357 fix(tui-gateway): merge agent output on model-switch history_version mismatch (#76870)

    merged to main

    files: contributors/emails/[redacted:email], tests/test_tui_gateway_server.py, tui_gateway/server.py

2 PRs closed without merging

From the close comments: merged via another change 2

  • #77021 fix(tui): snapshot history after pending model switch applies (#76870) · merged via another change → #77324
  • #77274 fix(tui-gateway): merge agent output on model-switch history_version mismatch (#76870) · merged via another change → #77357
Closed issues · 1
  • Closed#76870[Bug]: Model switch mid-session triggers history_version mismatch — all subsequent agent output discarded (empty assistant messages in DB)
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.40: 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
#77324, #77357
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
3 Aug 2026

For your agent

The same facts, typed.