Cairn
NousResearch/hermes-agent

Copilot Responses connection-scoped ID replay bug

Cluster 32716 · agent. Data as of

Nothing open on GitHub. Fix merged in #62495 on 11 Jul 2026. Check it covers your case.

The short answer

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

A bug where message-item IDs from one Copilot Responses API connection are incorrectly replayed on a different connection or credential, causing 401 errors. The members cover the bug report and multiple fix attempts addressing ID stripping or prevention on replay.

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.

  • #62495 fix(codex): prevent connection-scoped Copilot ID replay

    merged to main

    files: agent/auxiliary_client.py, agent/codex_responses_adapter.py, agent/conversation_loop.py, agent/transports/codex.py, tests/agent/test_auxiliary_client.py, tests/agent/test_codex_responses_adapter.py, tests/agent/transports/test_codex_transport.py, tests/run_agent/test_run_agent_codex_responses.py

2 PRs closed without merging

From the close comments: merged via another change 1 · stale or abandoned 1

  • #32725 fix(agent): strip connection-bound message ids on Copilot Responses replay · stale or abandoned
  • #62242 fix(codex): never replay message-item id on Copilot Responses connections · merged via another change → #62495
Closed issues · 1
  • Closed#32716[Bug]: Copilot Responses API 401 'input item ID does not belong to this connection' on assistant codex_message_items replay across credential/connection changes
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

Subsystem
agent
Merged PRs
#62495
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
11 Jul 2026

For your agent

The same facts, typed.

cluster/32716.json
cluster/32716.md