# NousResearch/hermes-agent · Gateway fallback provider model selection issues

## Open now

- Nothing open on GitHub.

These items appear to concern the gateway's fallback behavior, specifically which model is used when a fallback provider or auth fallback applies. One issue reports the primary model being retained instead of the fallback model, and two titles are fix-oriented changes about honoring the configured or fallback model; their outcomes are 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

- #19411: Gateway fallback provider keeps primary model instead of fallback model

## Prior & competing PRs

- **#19412: fix: use configured model for gateway auth fallback**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#19411`
- **#20992: fix(gateway): honor fallback provider model**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `f7b71aa0daf4acd56dba7e9c6aee1aa8cfe477a1`, `#19412`, `#19411`

## Fix status

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