Misleading error message in headless environment

[sebastianbenz]

Describe the bug
When running the MCP server in a headless container (e.g. cloudtop), the error message is:

 MCP tool 'new_page' reported tool error for function call: {"name":"new_page","args":{"url":"https://example.com"}} with response: [{"functionResponse":{"name":"new_page","response":{"error":{"content":[{"type":"text","text":"The browser is already running for                                                                 │
 │    ...... Use --isolated to run multiple browser instances."}],"isError":true}}}}]

Using --isolated is the wrong suggestion here. We should have a better

To Reproduce
Use default config with Gemini CLI in a headless container (e.g. cloudtop for googlers) and run a simple prompt like: "Check performance of example.com"

Expected behavior
There should be an error message that explains that the MCP server is running in a headless environment and needs the headless flag.

[AlfredoDinunzioTR]

Interesting. I started using this MCP on 10/8 and I did get it working in WSL.

Now today on 10/10, no matter what I do, I get

Error: The browser is already running for /home/user/.cache/chrome-devtools-mcp/chrome-profile. Use --isolated to run
     multiple browser instances.

Edit: I was able to resolve the error by rolling back to 0.6.1