Custom provider model id handling in model picker
Cluster 68347 · agent. Data as of
Nothing open on GitHub. Fix merged in #71144 on 25 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #71144. 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
- Nothing open on GitHub.
The members appear to concern custom providers where the model picker may supply a prefixed provider/model string rather than the configured model id field. One issue describes this behavior, and two pull request titles refer to fixes for model id resolution or prefix handling.
Open issues0
Open PRs0
Fixes on record
-
#71144 fix(model_switch): don't send a picker prefix as the custom provider model id
files:
contributors/emails/[redacted:email],hermes_cli/model_switch.py,tests/hermes_cli/test_model_switch_custom_providers.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#68436 fix(models): resolve custom provider model ids · merged via another change →
#71144
Closed issues · 1
- Closed#68347custom_providers ignores model id field when selecting from model picker; sends prefixed provider/model string instead
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
- agent
- Merged PRs
- #71144
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 25 Jul 2026