Auxiliary client missing provider alias resolution
Cluster 115006. Data as of
Nothing open on GitHub. Fix merged in #116686 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 #116686. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116686. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where the auxiliary client's provider alias lookup does not consult the authoritative auth table, causing providers like 'opencode' to appear unavailable for auxiliary tasks. Several fixes address how aux tasks resolve provider aliases.
Open issues0
Open PRs0
Fixes on record
-
#116686 fix(auxiliary): aux tasks resolve a client for every provider alias the main path accepts, e.g. opencode (#115006, salvage #115008)
files:
agent/auxiliary_client.py,tests/agent/test_auxiliary_client.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#115006[Bug]: auxiliary_client's _PROVIDER_ALIASES mirror is missing the OpenCode family — aux tasks report a working 'opencode' main provider as unavailable
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
- #116686
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 20 Sep 2026