feat: Allow opting out of default Chrome launch arguments #729
+54
−7
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.
Related Issue - #430
Description
When Chrome is launched via Puppeteer, it automatically adds a set of default flags like
--enable-automation --disable-extensions --disable-component-extensions-with-background-pages.Currently, there is no way to opt out of these defaults, which makes certain use cases difficult or impossible to support. this PR adds a way to selectively ignore specific default Chrome launch flags applied by Puppeteer using its ignoreDefaultArgs property.
{ "name": "chrome-devtools-mcp", "version": "latest", "mcpServers": { "chrome-devtools": { "command": "npx", "args": [ "chrome-devtools-mcp@latest", "--ignore-default-chrome-arg='--enable-automation'", "--ignore-default-chrome-arg='--disable-extensions'" ] } } }