fix(mcp): enable the chromium sandbox for the default browser#41652
Merged
Conversation
`validateBrowserConfig` defaults `chromiumSandbox` to `true`, but it gated that on `browser.browserName` instead of the resolved local `browserName`: `browser.browserName` is `undefined` with no `--browser` while the local `browserName` is defaulted to `chromium`, so the block was skipped and `chromiumSandbox` stayed `undefined` launching then adds `--no-sandbox` whenever `chromiumSandbox !== true`, so the default MCP session ran Chrome with the sandbox disabled, unlike an identical `--browser=chrome` session use the resolved `browserName`, matching the sibling chromium block a few lines below
Contributor
Test results for "MCP"1 failed 7645 passed, 1142 skipped Merge workflow run. |
pavelfeldman
approved these changes
Jul 7, 2026
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
2 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.
validateBrowserConfigdefaultschromiumSandboxtotrue, but it gated that onbrowser.browserNameinstead of the resolved localbrowserName:browser.browserNameisundefinedwith no--browserwhile the localbrowserNameis defaulted tochromium, so the block was skipped andchromiumSandboxstayedundefinedlaunching then adds
--no-sandboxwheneverchromiumSandbox !== true, so the default MCP session ran Chrome with the sandbox disabled, unlike an identical--browser=chromesessionuse the resolved
browserName, matching the sibling chromium block a few lines below