Fallback provider config and runtime fix bugs
Cluster 24092 · hermes cli. Data as of
2 open items. Fix attempted, not merged.
The short answer
- Known?
- Yes. 5 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and fixes address bugs in fallback provider resolution, including incorrect base_url and api_key_env propagation, custom provider handling, and related runtime/CLI override persistence issues. The members share a theme of provider configuration correctness but span several distinct sub-problems.
Open issues1
- Issue#24092[Bug]: fallback_providers with provider: custom + explicit base_url falls back to OpenRouter when main model.provider is a named provider
Open PRs1
- PR#24113fix(cli): preserve custom fallback runtime overrides
Fixes on record
-
#5269 fix: Ollama Cloud auth, /model switch persistence, and alias tab completion
2 PRs closed without merging
From the close comments: merged via another change 2
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.40: 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
- #5269
- Closed issues
- 0
- Attempts
- 2 PRs closed without merging