Cairn
NousResearch/hermes-agent

GPT-5 custom providers missing Responses API auto-upgrade

Cluster 23893 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and fixes address a bug where custom providers serving GPT-5.x models are not automatically upgraded to the Responses API (codex_responses), unlike first-party providers. Multiple fix attempts and bug reports describe the same underlying gap in the auto-upgrade logic.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: other 2

  • #10828 fix(runtime): auto-upgrade GPT-5 named custom providers to codex_responses · other → #10814
  • #23895 fix: allow Responses API auto-upgrade for custom providers serving GPT-5.x · other
Closed issues · 1
  • Closed#23893GPT-5.x models on custom providers never auto-upgrade to Responses API
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

Subsystem
agent
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/23893.json
cluster/23893.md