feat: Auto-connect to existing Chrome when profile is locked#8
Open
Alllynnn wants to merge 1 commit into
Open
Conversation
When a second MCP instance attempts to launch Chrome with the same user data directory, instead of throwing an error, it now automatically connects to the already-running browser via WebSocket. - Add --remote-debugging-port=0 on launch so Chrome writes DevToolsActivePort with a random local port - Add connectToExistingBrowser() to read the port file and connect - Modify catch block to attempt connection before falling back to error
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.
Summary
--remote-debugging-port=0，使 Chrome 写入DevToolsActivePort文件（含随机本地端口）connectToExistingBrowser()辅助函数，读取端口文件并通过puppeteer.connect()接入--isolated/--browserUrl/--wsEndpoint路径完全不受影响Test plan
npm run build编译通过--isolated模式行为不变