NousResearch/hermes-agent

Model switching by name with custom providers

Cluster 5569 · 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.

The three members appear to share a theme: switching models by name when user-defined or custom providers are configured, including a Telegram model switcher report that it defaults to the currently selected provider. Two members are titled as fixes, but the titles alone do not show their scope or outcome.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #5611 fix(models): resolve custom providers when switching models by name (… · done elsewhere → 791c992, #5569, #5611, #5644
  • #5644 fix(model): resolve user-defined provider when switching by default_model name · other → 791c992, #45006
Closed issues · 1
  • Closed#5569[Bug]: Telegram model switcher defaults to currently selected provider when choosing a new model by name with multiple custom providers present
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.