Protocol error (Target.setDiscoverTargets): Target closed.

[valmedia]

Description of the bug

According to puppeteer/puppeteer#6258, this error hides the real error so need to set pipe: false to see the real error. It would be nice to have the option to set pipe: false.

Reproduction

No response

Expectation

No response

MCP configuration

No response

Chrome DevTools MCP version

0.9.0

Chrome version

No response

Coding agent version

No response

Model version

No response

Chat log

No response

Node version

No response

Operating system

None

Extra checklist

• I want to provide a PR to fix this bug

[jonit-dev]

same

[OrKoN]

Thanks for reporting, but I do not think the issue puppeteer/puppeteer#6258 is right about that. Could you clarify the steps to reproduce the issue and if you get additional details by setting the --logFile command line argument (https://github.com/ChromeDevTools/chrome-devtools-mcp?tab=readme-ov-file#configuration) + the environment variable DEBUG=puppeteer:* when launching the MCP server?