/model switching and provider selection for shared model names
Cluster 48731 · hermes cli. Data as of
1 open item. Fix merged in #107236 on 10 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- A fix was merged to main in PR #107236. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 0 PRs.
Next step: read #107236, then check whether your report is the one still open.
Read #107236Pick up a Lab taskThree members concern how the /model command picks a provider when switching to a model name that more than one provider may serve. They touch on keeping a model the current provider serves, checking the configured provider catalog before static detection, and a report that a native provider is preferred over the current reseller; one also mentions the deepseek-flash id.
Open issues1
- Issue#48731/model switch to shared model name prefers native provider over current reseller
Open PRs0
Fixes on record
-
#107236 fix(models): /model keeps a model the current provider serves; deepseek-flash is DeepSeek's canonical Flash id (refs #97487, supersedes #107126)
files:
agent/model_metadata.py,agent/reasoning_timeouts.py,agent/usage_pricing.py,contributors/emails/[redacted:email],hermes_cli/goals.py,hermes_cli/model_normalize.py,hermes_cli/models.py,hermes_cli/models_catalog_static.py,hermes_cli/models_detect.py,plugins/model-providers/deepseek/__init__.py,tests/agent/test_model_metadata.py,tests/agent/test_reasoning_stale_timeout_floor.py,tests/agent/test_usage_pricing.py,tests/hermes_cli/test_model_normalize.py,tests/hermes_cli/test_models_detect_live_catalog.py,tests/plugins/model_providers/test_deepseek_profile.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#48744 fix(cli): check configured provider catalog before static detection in /model switch · superseded by another PR →
2466684,#107236
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.00means 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 LabAt a glance
- Subsystem
- hermes cli
- Merged PRs
- #107236
- Closed issues
- 0
- Attempts
- 1 PR closed without merging
- Fix link checked
- 10 Sep 2026