docs: Remove information regarding conflicts between autoConnect/browser-url and extension debugging.

Author: natorion

docs/troubleshooting.md

@@ -108,7 +108,3 @@ If you are using the `--autoConnect` flag and tools like `list_pages`, `new_page
 2. Remote debugging is enabled in Chrome via `chrome://inspect/#remote-debugging`.
 3. You have allowed the remote debugging connection prompt in the browser.
 4. There is no other MCP server or tool trying to connect to the same debugging port.
-
-### Conflicts with Extension Debugging
-
-Extension debugging is not supported when using `--browserUrl` (`--browser-url`) and `--autoConnect`. These options are mutually exclusive to the `--enableCategoryExtensions` (if applicable) or general extension debugging features. Attempting to use them together will result in connection failures or undefined behavior.

skills/troubleshooting/SKILL.md

@@ -56,14 +56,12 @@ Read the contents of https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/
 - Sandboxing restrictions (macOS Seatbelt, Linux containers).
 - WSL requirements.
 - `--autoConnect` handshakes, timeouts, and requirements (requires **running** Chrome 144+).
-- Conflicts between `--autoConnect`/`--browser-url` and extension debugging.
 
 ### Step 4: Formulate a Configuration
 
 Based on the exact error and the user's environment (OS, MCP client), formulate the correct MCP configuration snippet. Check if they need to:
 
 - Pass `--browser-url=http://127.0.0.1:9222` instead of `--autoConnect` (e.g. if they are in a sandboxed environment like Claude Desktop).
-- Remove `--enableCategoryExtensions` if using `--autoConnect`.
 - Enable remote debugging in Chrome (`chrome://inspect/#remote-debugging`) and accept the connection prompt. **Ask the user to verify this is enabled if using `--autoConnect`.**
 - Add `--logFile <absolute_path_to_log_file>` to capture debug logs for analysis.
 - Increase `startup_timeout_ms` (e.g. to 20000) if using Codex on Windows.