CLI model string fails to route custom providers
Cluster 73943 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #115293 on 18 Sep 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 #115293. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #115293. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where specifying a custom provider via the -m/--model flag sends requests to the default cloud provider instead, along with a fix to correctly parse provider:model syntax in the CLI.
Open issues0
Open PRs0
Fixes on record
-
#115293 CLI/oneshot/TUI: -m custom:<name>:<model> reaches that provider instead of egressing to the default (#73943, credit #74082)
files:
hermes_cli/model_switch.py,hermes_cli/models.py,hermes_cli/oneshot.py,tests/hermes_cli/test_startup_model_routing.py,tui_gateway/server.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#74214 fix(cli): parse provider:model syntax in -m/--model, not just the /model command · superseded by another PR →
#75311
Closed issues · 1
- Closed#73943Selecting a custom provider sends the prompt to the default cloud provider (providers: entries unreachable by model string)
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
- #115293
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 18 Sep 2026