Stale credential reuse during primary runtime restore
Cluster 25205 · agent. Data as of
Nothing open on GitHub. Fix merged in #53913 on 28 Jun 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 #53913. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #53913. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where _restore_primary_runtime bypasses the credential pool and reuses a potentially revoked API key, along with associated fixes to re-select from the pool on restore.
Open issues0
Open PRs0
Fixes on record
-
#53913 fix(pool): re-select from credential pool on primary runtime restore
files:
agent/agent_runtime_helpers.py,scripts/release.py,tests/agent/test_restore_primary_pool_reselect.py,tests/run_agent/test_24996_fallback_exhaustion_cooldown.py,tests/test_tui_gateway_server.py,tests/tools/test_process_registry.py
2 PRs closed without merging
From the close comments: merged via another change 2
Closed issues · 1
- Closed#25205[Bug] _restore_primary_runtime bypasses credential pool, reuses stale (revoked) api_key
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
- #53913
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 28 Jun 2026