Chrome DevTools for coding agents
docs: document mcp client sandboxing (#65)
Alex Rudenkobfbdada6c7d5
diff --git a/README.md b/README.mdindex 16cbf7b8..1be7ddb0 100644--- a/README.md+++ b/README.md@@ -204,3 +204,14 @@ The user data directory is not cleared between runs and shared acrossall instances of `chrome-devtools-mcp`. Set the `isolated` option to `true`to use a temporary user data dir instead which will be cleared automatically afterthe browser is closed.++## Known limitations++### Operating system sandboxes++Some MCP clients allow sandboxing the MCP server using macOS Seatbelt or Linux+containers. If sandboxes are enabled, `chrome-devtools-mcp` is not able to start+Chrome that requires permissions to create its own sandboxes. As a workaround,+either disable sandboxing for `chrome-devtools-mcp` in your MCP client or use+`--connect-url` to connect to a Chrome instance that you start manually outside+of the MCP client sandbox.