Avoid blocking thread startup on MCP OAuth discovery - #32825
Merged
copyberry[bot] merged 1 commit intoJul 13, 2026
Merged
Conversation
## Why OAuth metadata discovery for an optional HTTP MCP server can stall, delaying `thread/start` even though that server is not required. ## What changed - Remove eager MCP authentication-status discovery from session and connection manager startup. - When an MCP connection reports an authentication error, inspect configured and stored credentials locally to preserve login and reauthentication failure reasons without making another discovery request. - Continue using server configuration directly for startup error messages and timeout hints. ## Testing Add an app-server regression test with an optional HTTP MCP endpoint that accepts a connection but never responds, and verify that `thread/start` completes without waiting for its configured startup timeout. GitOrigin-RevId: 56fe0188cc1ceaf746b0b65e8b7dd1fd2e13420d
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/56fe0188cc1ceaf746b0b65e8b7dd1fd2e13420d
branch
from
July 13, 2026 15:48
8c800bf to
2e156cb
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/56fe0188cc1ceaf746b0b65e8b7dd1fd2e13420d
branch
July 13, 2026 15:49
NathanDrake2406
temporarily deployed
to
issue-triage
July 13, 2026 15:59 — with 
GitHub Actions
Inactive
NathanDrake2406
temporarily deployed
to
issue-triage
July 13, 2026 15:59 — with
GitHub Actions
Inactive
NathanDrake2406
temporarily deployed
to
issue-triage
July 13, 2026 15:59 — with
GitHub Actions
Inactive
srmarron-star
temporarily deployed
to
issue-triage
July 13, 2026 16:32 — with
GitHub Actions
Inactive
srmarron-star
temporarily deployed
to
issue-triage
July 13, 2026 16:32 — with
GitHub Actions
Inactive
srmarron-star
temporarily deployed
to
issue-triage
July 13, 2026 16:32 — with
GitHub Actions
Inactive
srmarron-star
temporarily deployed
to
issue-triage
July 13, 2026 16:33 — with
GitHub Actions
Inactive
JerWritesCode
temporarily deployed
to
issue-triage
July 13, 2026 16:39 — with
GitHub Actions
Inactive
JerWritesCode
temporarily deployed
to
issue-triage
July 13, 2026 16:39 — with
GitHub Actions
Inactive
JerWritesCode
temporarily deployed
to
issue-triage
July 13, 2026 16:39 — with
GitHub Actions
Inactive
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
10 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Avoid blocking thread startup on MCP OAuth discovery
Why
OAuth metadata discovery for an optional HTTP MCP server can stall, delaying
thread/starteven though that server is not required.What changed
manager startup.
stored credentials locally to preserve login and reauthentication failure
reasons without making another discovery request.
timeout hints.
Testing
Add an app-server regression test with an optional HTTP MCP endpoint that accepts
a connection but never responds, and verify that
thread/startcompletes withoutwaiting for its configured startup timeout.