NousResearch/hermes-agent

Stale reasoning leakage across turns or models

Cluster 95834. Data as of 2026-10-30 11:57 UTC

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

open issues

open PRs

items grouped

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

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

Read #111181 Pick up a Lab task

These items address a bug where reasoning items or encrypted content from one model or turn incorrectly persist and appear in subsequent turns or for co-hosted models on OpenAI-compatible endpoints. The work involves scoping reasoning replay to the originating model and handling foreign message IDs.

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.

#111181 Codex Responses replay drops foreign message ids and scopes reasoning replay to the issuing model (#92311, #95834, salvage #92325 #95849)

merged to main

files: agent/auxiliary_client.py, agent/codex_responses_adapter.py, agent/error_classifier.py, agent/transports/codex.py, tests/agent/test_codex_responses_adapter.py, tests/agent/test_error_classifier.py, tests/agent/transports/test_codex_transport.py

1 PR closed without merging

From the close comments: merged via another change 1

#95849 fix(agent): stop co-hosted models from inheriting stale reasoning · merged via another change → 14a93d6, #111181

Closed issues · 1

Closed#95834[Bug]: Stale encrypted_content reasoning items leak across turns on OpenAI-compatible endpoints using codex_responses api_mode

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.67: 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: #111181
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 15 Sep 2026

For your agent

The same facts, typed.

cluster/95834.json
cluster/95834.md