Custom provider configuration being ignored or misresolved at runtime
Cluster 8919 · agent. Data as of
Nothing open on GitHub. Fix merged in #50385 on 21 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 #50385. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #50385. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items all concern custom provider settings in config (such as model.api_base aliasing to base_url, nested config handling, and provider/credential resolution) not being honored at runtime. One is a bug report and the others are fix-oriented changes; the titles alone do not show their outcomes.
Open issues0
Open PRs0
Fixes on record
-
#50385 fix(config): honor model.api_base for custom providers (alias to base_url)
files:
hermes_cli/config.py,tests/cli/test_cli_init.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
-
#8963 fix(config): restore custom provider resolution and nested config han… · done elsewhere →
824c9d3,#50385,#8919 -
#35056 fix(provider): unify provider/credential resolution — config.yaml as single source, fail-closed on custom intent · merged via another change →
#4600,#5358,#8919,#12146,#27132,#13489,#3263,#29285
Closed issues · 1
- Closed#8919Bug: custom provider config ignored at runtime
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
- #50385
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 21 Jun 2026