Cairn
NousResearch/hermes-agent

Custom provider config versus OpenRouter catalog precedence in model selection

Cluster 39753 · hermes cli. Data as of

3 open items. Fix attempted, not merged.

The short answer

0open issues
3open PRs
8items grouped
Known?
Yes. 8 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 4 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
0 issues and 3 PRs.

The members largely concern model/provider resolution, where an explicitly configured custom provider (provider, base_url, or custom_providers match) may be overridden by OpenRouter catalog auto-detection. Most titles propose respecting explicit config first or skipping the OpenRouter lookup for custom providers; some appear to be duplicates.

Open issues0

No open issues.

Open PRs3

  • PR#39803fix(models): respect custom provider catalog priority
  • PR#50277fix(models): respect config.model provider+base_url before OpenRouter auto-detect
  • PR#50280fix(model_switch): respect explicit provider config over OpenRouter catalog

4 PRs closed without merging

From the close comments: superseded by another PR 2 · done elsewhere 1 · duplicate 1

  • #39874 fix(models): skip OpenRouter catalog lookup when provider is 'custom' · duplicate → #39803, #39753
  • #44663 fix(model_switch): respect explicit provider config over OpenRouter catalog · superseded by another PR → #50280, #45552
  • #45434 fix(models): respect config.model provider+base_url before OpenRouter auto-detect · superseded by another PR → #50277
  • #50868 fix(runtime_provider): honor custom_providers model match when UI rewrote model.provider · done elsewhere → 791c992, #45006
Closed issues · 1
  • Closed#39753config priority: OpenRouter catalog overrides explicit custom provider
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.25: 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
hermes cli
Closed issues
1
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/39753.json
cluster/39753.md