Cross-process locking for MCP OAuth token refresh
Cluster 71335 · agent. Data as of
Nothing open on GitHub. Fix merged in #111186 on 15 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 #111186. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111186. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where concurrent agent processes sharing the same HERMES_HOME directory corrupt rotating OAuth tokens due to missing cross-process file locking during MCP token refresh. The members cover the bug report and two related fixes addressing serialization and file locking.
Open issues0
Open PRs0
Fixes on record
-
#111186 MCP OAuth refresh is fenced across processes so a rotated refresh token is presented exactly once (#71335, salvage #94846)
files:
tests/tools/test_mcp_oauth.py,tests/tools/test_mcp_oauth_manager.py,tools/mcp_oauth.py,tools/mcp_oauth_provider.py
2 PRs closed without merging
From the close comments: merged via another change 1 · superseded by another PR 1
Closed issues · 1
- Closed#71335[Bug][auth] Concurrent agent processes sharing HERMES_HOME corrupt rotating MCP OAuth grants (Notion) — no cross-process lock on mcp-tokens
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
- #111186
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 15 Sep 2026