Cairn
NousResearch/hermes-agent

Gateway fallback provider model selection issues

Cluster 19411 · gateway. 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 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.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1

  • #19412 fix: use configured model for gateway auth fallback · duplicate → #19411
  • #20992 fix(gateway): honor fallback provider model · done elsewhere → f7b71aa, #19412, #19411
Closed issues · 1
  • Closed#19411Gateway fallback provider keeps primary model instead of fallback model
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
gateway
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/19411.json
cluster/19411.md