Auxiliary vision custom provider loses API key bug
Cluster 76602 · agent. Data as of
Nothing open on GitHub. Fix merged in #131915 on 3 Oct 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 #131915. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #131915. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where auxiliary vision configured with a named custom provider and explicit base_url loses its API key by incorrectly downgrading the provider identity. Two fix attempts address preserving the named user-defined provider when base_url is explicitly set.
Open issues0
Open PRs0
Fixes on record
-
#131915 fix(auxiliary_client): preserve named user-defined provider on explicit base_url [risk 0.30]
files:
agent/auxiliary_client.py,tests/agent/test_auxiliary_client.py
2 PRs closed without merging
From the close comments: partial fix 2
Closed issues · 1
- Closed#76602auxiliary vision with custom provider + base_url loses api_key (downgraded to 'custom' → 'no-key-required' → 401)
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
- #131915
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 3 Oct 2026