Fix local provider alias routing to correct base_url
Cluster 115990. Data as of
Nothing open on GitHub. Fix merged in #116688 on 20 Sep 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 #116688. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116688. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address a bug where named local-server aliases in provider configuration lose their base_url and incorrectly route requests to a remote provider. The changes ensure local fallback and auxiliary client resolution respects the configured endpoint.
Open issues0
Open PRs0
Fixes on record
-
#116688 fix(auxiliary): a providers: entry named like a local-server alias (llamacpp) resolves aux clients to its base_url (#115990, salvage #116003)
files:
agent/auxiliary_client.py,tests/agent/test_auxiliary_named_custom_providers.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#115990Fallback entry referencing a named provider from `providers:` loses its base_url and routes a local model to Gemini (HTTP 404)
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
- Merged PRs
- #116688
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 20 Sep 2026