# NousResearch/hermes-agent · Auto-upgrade GPT-5 named custom providers to responses API

## Open now

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

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

- #10814: \[Bug\]: auxiliary named custom providers do not auto-upgrade GPT-5 models to codex_responses

## Prior & competing PRs

- **#10827: fix: auto-upgrade GPT-5 named custom providers to responses API**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#10828`
- **#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`

## Fix status

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