Curated MCP sync fails when an existing thread switches authentication mode
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
The app-server integration test suite::v2::mcp_server_status::existing_thread_loads_api_curated_mcp_after_auth_switch_sync fails on the current upstream main when an existing thread changes authentication mode and curated MCP/plugin synchronization is expected to update its server state.
Observed focused result:
cargo nextest run -p codex-app-server -E "test(existing_thread_loads_api_curated_mcp_after_auth_switch_sync)"
The test reaches its deadline waiting for the expected post-switch sync. This appears related to the auth-mode-specific curated marketplace work in PRs #28383 and #35671, but no existing issue covers this regression. Please restore the expected synchronization and make the test pass without relying on a long timeout.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the focused cargo nextest command for suite::v2::mcp_server_status::existing_thread_loads_api_curated_mcp_after_auth_switch_sync and read that test. Trace the existing-thread authentication switch and curated MCP synchronization path, then confirm the expected post-switch server state is reached without relying on a long timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authentication, backend, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100