Config model key alias bug and fix attempts
Cluster 3535 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #3603 on 28 Mar 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 #3603. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #3603. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where the 'model' key in config.yaml model section is silently ignored in favor of a hardcoded default, along with multiple related fix attempts to accept 'model' as an alias for 'default'.
Open issues0
Open PRs0
Fixes on record
-
#3603 fix(config): accept 'model' key as alias for 'default' in model config
files:
cli-config.yaml.example,cli.py,gateway/run.py,hermes_cli/runtime_provider.py,website/docs/user-guide/configuration.md
2 PRs closed without merging
From the close comments: merged via another change 1 · superseded by another PR 1
Closed issues · 1
- Closed#3535[Bug]: config.yaml model.model key is silently ignored — falls back to hardcoded default
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
- hermes cli
- Merged PRs
- #3603
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 28 Mar 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.