Fix duplicate local MCP servers on startup - #3405
Open
mohitdebian wants to merge 1 commit into
Open
Conversation
Contributor
|
@mohitdebian is attempting to deploy a commit to the Different AI Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
PR Title
Fix duplicate local MCP servers on startup
PR Body
Fixes #3325
Description
This PR resolves an issue where the Node.js server would mistakenly double-register the primary workspace's local MCP servers during the startup sequence. Because the embedded engine natively loads
opencode.jsonon boot, the subsequent loop pushing all workspace MCPs via the REST API caused duplicate background processes to spawn.Changes Made
syncAllWorkspacesRuntimeMcpToEngineto bypass network POST requests specifically for the primary workspace.syncRuntimeMcpToOpencodeEngineto mock an initial"connected"registration status for the bypassed workspace so the UI immediately reflects the correct state before the first SSE ping arrives.mcp.engine-sync.e2e.test.tsandagent-context-diagnostics.test.tsto expect the network bypass behavior.Testing
mcp.engine-sync.e2e.test.tsandagent-context-diagnostics.test.ts) updated and passing.