NousResearch/hermes-agent

Codex message ID handling across provider switches

Cluster 92311. Data as of 2026-10-25 11:21 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. 4 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 issues and fixes concern a bug where Codex sessions break with 400 errors when replaying message IDs from a different provider mid-session, particularly IDs not starting with 'msg'. The work addresses guarding and scoping message IDs correctly when switching providers.

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

2 PRs closed without merging

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

#92325 fix(codex): keep sessions usable after provider switches · merged via another change → 14a93d6, #111181
#97246 fix(agent): guard Codex message IDs across providers · done elsewhere → f7b6a2b, #92311, #92325

Closed issues · 1

Closed#92311[Bug]: Codex Responses 400 when replaying foreign input[].id that does not start with msg after mid-session provider switch

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

For your agent

The same facts, typed.

cluster/92311.json
cluster/92311.md