Auth fallback config bypasses secret scope isolation
Cluster 74311 · agent. Data as of
Nothing open on GitHub. Fix merged in #74340 on 1 Aug 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 #74340. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #74340. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug was identified where fallback configuration resolves API keys using raw os.getenv(), bypassing secret_scope profile isolation. These members track the problem and proposed fixes to use secret-scope-aware secret resolution instead.
Open issues0
Open PRs0
Fixes on record
-
#74340 fix(auth): restore secret-scope isolation for fallback API key resolution
files:
agent/agent_init.py,agent/auxiliary_client.py,agent/chat_completion_helpers.py,hermes_cli/fallback_config.py,tests/hermes_cli/test_fallback_config.py
2 PRs closed without merging
From the close comments: superseded by another PR 2
Closed issues · 1
- Closed#74311auth: fallback config resolves API key via raw os.getenv(), bypassing secret_scope profile isolation
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
- #74340
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 1 Aug 2026