NousResearch/hermes-agent

Fix reasoning field encoding when forking sessions

Cluster 57240 · agent. Data as of

Nothing open on GitHub. Fix merged in #82109. 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 #82109. 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.

These issues and pull requests address a bug where forking a session causes reasoning columns to be double-encoded or dropped, resulting in silent loss of reasoning replay in forked branches.

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.

  • #82109 fix(state,cli,tui-gateway): keep reasoning fields intact across forks and branches (#57240)

    merged to main

    files: hermes_cli/cli_commands_mixin.py, hermes_state.py, tests/cli/test_branch_command.py, tests/hermes_state/test_reasoning_roundtrip.py, tests/test_tui_gateway_server.py, tui_gateway/methods_session.py, tui_gateway/server.py

3 PRs closed without merging

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

  • #57248 fix(state,cli,tui-gateway): keep reasoning fields intact across forks and branches · merged via another change → #82109
  • #57454 fix(state): preserve reasoning fields when forking sessions · done elsewhere → #82109, #57248
  • #57536 fix(state): avoid double-encoding reasoning columns on fork round-trip · superseded by another PR → #57704, #31829, #35327, #57548, #28154, #57713, #31365, #57536, #57248, #57696, #47821
Closed issues · 1
  • Closed#57240forking a session double-encodes the reasoning columns — forked sessions silently lose reasoning replay
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

Subsystem
agent
Merged PRs
#82109
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
9 Aug 2026

For your agent

The same facts, typed.