NousResearch/hermes-agent
JSON session export missing conversation history fix
Cluster 2229 · gateway. Data as of
Nothing open on GitHub. Fix attempted, not merged.
The short answer
0open issues
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and PRs concern a bug where tool_calls and conversation history are lost when exporting sessions as JSON. The members focus on identifying and addressing the missing conversation_history field in JSON session exports.
Open issues0
Open PRs0
3 PRs closed without merging
From the close comments: duplicate 1 · won't fix / by design 1 · other 1
- #2237 fix: include conversation_history in JSON session export to prevent message loss · duplicate
-
#2239 fix(agent): include conversation_history in JSON session export to prevent message loss · won't fix / by design →
#2229 - #26550 fix(session): include conversation_history in JSON session export (#2229) · other
Closed issues · 1
- Closed#2229bug(gateway): legacy JSON session exports lose tool_calls, creating broken conversation history
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.00means 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 LabAt a glance
- Subsystem
- gateway
- Closed issues
- 1
- Attempts
- 3 PRs closed without merging