# NousResearch/hermes-agent · GPT-5 custom providers missing Responses API auto-upgrade

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #23893: GPT-5.x models on custom providers never auto-upgrade to Responses API

## Prior & competing PRs

- **#10828: fix(runtime): auto-upgrade GPT-5 named custom providers to codex_responses**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#10814`
- **#23895: fix: allow Responses API auto-upgrade for custom providers serving GPT-5.x**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`

## Fix status

- No merged fix on record.
- Subsystem: `agent`