Fix duplicate provider matches in /model command
Cluster 112788. Data as of
Nothing open on GitHub. Fix merged in #113804 on 17 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #113804. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #113804. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address a bug where the /model command's fuzzy matching incorrectly treats compatibility views of the same provider as distinct entries. The fixes deduplicate such matches and preserve custom session identifiers.
Open issues0
Open PRs0
Fixes on record
-
#113804 fix(model-switch): /model collapses compat views of one provider by identity and keeps custom:<slug> sessions (closes remaining atoms of #112788)
files:
hermes_cli/model_switch.py,tests/hermes_cli/test_model_switch_configured_provider_routing.py
2 PRs closed without merging
From the close comments: duplicate 1 · other 1
Closed issues · 1
- Closed#112788[Bug] /model fuzzy matching treats compatibility views of one provider as two providers
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.50: 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
- Merged PRs
- #113804
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 17 Sep 2026