Handling model.name config key and model name forwarding
Cluster 34500 · agent. Data as of
Nothing open on GitHub. Fix merged in #54093 on 28 Jun 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 #54093. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #54093. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Most members concern how the model.name config key is treated, with titles describing alias, honoring, or canonicalization to model.default. One member reports a model name not being forwarded to the API request for custom providers, which appears related but is described differently.
Open issues0
Open PRs0
Fixes on record
-
#54093 fix(config): canonicalize model.name/model.model to model.default (#34500)
files:
gateway/run.py,hermes_cli/config.py,infographic/model-name-canon/infographic.png,tests/cli/test_cli_init.py
2 PRs closed without merging
From the close comments: done elsewhere 2
Closed issues · 1
- Closed#34500custom_providers: model name not forwarded to API request
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
- Subsystem
- agent
- Merged PRs
- #54093
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 28 Jun 2026