Cairn
NousResearch/hermes-agent

Auto-upgrade GPT-5 named custom providers to responses API

Cluster 10814 · 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.

Three members (two fixes and one bug report) concern named custom providers using GPT-5 models not being automatically switched to the codex_responses/responses API mode. One report specifically mentions auxiliary providers; the status of any change is not stated in the titles.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #10827 fix: auto-upgrade GPT-5 named custom providers to responses API · duplicate → #10828
  • #10828 fix(runtime): auto-upgrade GPT-5 named custom providers to codex_responses · other → #10814
Closed issues · 1
  • Closed#10814[Bug]: auxiliary named custom providers do not auto-upgrade GPT-5 models to codex_responses
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/10814.json
cluster/10814.md