Cairn

Filter session_meta from chat-completions payload

NousResearch/hermes-agent · cluster 4715 · agent

Data as of

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

The short answer

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

These issues and fixes address a bug where transcript-only session_meta entries leak into chat-completions payloads during session restore or resume, causing validation errors. Multiple fixes target filtering these roles from CLI, gateway, and history contexts.

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.

  • #4880 fix: filter transcript-only roles from chat-completions payload

    merged to main

    files: cli.py, run_agent.py, tests/test_session_meta_filtering.py

2 PRs closed without merging

From the close comments: closed without comment 1 · merged via another change 1

  • #4717 fix: filter transcript-only roles from chat-completions payload · merged via another change → #4880
  • #4790 fix(cli): fully filter session_meta from restored conversations · closed without comment
Closed issues · 2
  • Closed#4715[Bug]: CLI resume/session restore can leak transcript-only `session_meta` into chat-completions payload
  • Closed#5364fix(gateway): /btw command fails with validation error due to session_meta in history
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.34: 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
#4880
Closed issues
2
Attempts
2 PRs closed without merging
Fix link checked
3 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.

For your agent

The same facts, typed.

cluster/4715.json
cluster/4715.md