mirror of
https://github.com/ChromeDevTools/chrome-devtools-mcp.git
synced 2026-09-14 19:45:30 +08:00
Julian Huang
d9a8cb6ec2
## Summary - Serialize `chrome-devtools start` arguments against the CLI defaults. - Preserve explicit false values such as `--headless=false` as `--no-headless`. - Add an end-to-end regression test for the forwarded daemon arguments. ## Problem The CLI defaults `headless` to true while the MCP server defaults it to false. The start command parsed an explicit false value correctly, but then serialized it against the server defaults. Because false matched the server default, the argument was dropped. The daemon subsequently reparsed the missing option in CLI mode and restored `headless=true`. Using the CLI option definitions for serialization keeps the default compact while forwarding explicit values that differ from the CLI default. ## Testing - `npm run test tests/e2e/chrome-devtools-start-stop.test.ts` - `npm run format` - `npm run test` (all relevant tests passed; the local full-suite run only failed the unrelated large full-page screenshot case because Chrome returned `Page is too large`) Co-authored-by: Natasha Gorshunova <47688881+nattallius@users.noreply.github.com>