Auth provider auto-detection misses profile-scoped API keys
Cluster 86917. Data as of
Nothing open on GitHub. Fix merged in #87708 on 16 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #87708. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #87708. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where provider auto-detection fails to resolve API keys scoped to non-default profiles, causing 'No LLM provider configured' errors. Two fix attempts address this resolution path through the profile scope.
Open issues0
Open PRs0
Fixes on record
-
#87708 fix(auth): resolve provider auto-detection keys through the profile scope (salvage #86918)
files:
AGENTS.md,hermes_cli/auth.py,tests/hermes_cli/test_auth_provider_scope.py,tests/test_gitlock.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#86918 fix(auth): resolve provider auto-detection keys through the profile scope (#86917) · merged via another change →
#87708,#86917
Closed issues · 1
- Closed#86917[Bug] multiplex: resolve_provider auto-detection ignores profile-scoped API keys — secondary profiles get 'No LLM provider configured'
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.67: 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
- #87708
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Aug 2026