NousResearch/hermes-agent

Fix reasoning item ID loss in Responses API replays

Cluster 97427. Data as of 2026-10-25 11:21 UTC

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

open issues

open PRs

items grouped

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

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

Read #115733 Pick up a Lab task

These issues and fixes address a bug where reasoning item IDs were stripped during message replay, causing 400 errors in GPT-5.6 Responses API continuations. The changes preserve ID symmetry and valid replay item graphs for prompt caching.

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.

#115733 fix(codex): GPT-5.6 Responses continuations no longer 400 on a replayed message whose reasoning id was stripped (#97427, #97442, salvage #97445)

merged to main

files: agent/codex_responses_adapter.py, agent/transports/codex.py, contributors/emails/[redacted:email], tests/agent/test_codex_responses_adapter.py, tests/agent/transports/test_codex_transport.py

2 PRs closed without merging

From the close comments: duplicate 1 · partial fix 1

#97777 fix(agent): Preserve reasoning and message ID symmetry for Responses API prompt caching · partial fix → #97427, #10217, #97445
#98942 fix(responses): preserve valid replay item graphs (#97427) · duplicate → #97445

Closed issues · 1

Closed#97427[Bug]: GPT-5.6 Responses rejects replayed assistant message when Hermes strips its required reasoning item ID

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.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: #115733
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 19 Sep 2026

For your agent

The same facts, typed.

cluster/97427.json
cluster/97427.md