fix: allow --categoryExtensions when connecting to an existing browser

Remove the categoryExtensions conflicts with autoConnect, browserUrl and
wsEndpoint added in #2753. Chrome 149+ supports extension debugging over
these connections, and 1.10.1 accepts the combination.

Update the --categoryExtensions help text, generated docs and the
troubleshooting skill to state the Chrome 149+ requirement for attach modes.

Fixes #2989

Author: paviad

docs/configuration.md

@@ -35,7 +35,7 @@ The Chrome DevTools MCP server supports the following configuration option:
   - **Default:** `true`
 
 - **`--categoryExtensions`/ `--category-extensions`**
-  Set to true to include tools related to extensions. Note: This feature is currently only supported with a pipe connection. autoConnect, browserUrl, and wsEndpoint are not supported with this feature until 149 will be released.
+  Set to true to include tools related to extensions. With autoConnect, browserUrl or wsEndpoint, this requires Chrome 149 or later.
   - **Type:** boolean
   - **Default:** `false`
 

skills/troubleshooting/SKILL.md

@@ -52,7 +52,7 @@ All tools in `chrome-devtools-mcp` are annotated with `readOnlyHint: true` (for
 If the tools related to extensions (like `install_extension`) are not available, or if the extensions you load are not functioning:
 
 1. **Check for the `--categoryExtensions` flag**: Ensure this flag is passed in the MCP server configuration to enable the extension category tools.
-2. **Make sure the MCP server in configured to launch Chrome instead of connecting to an instance**: Chrome before 149 is not able to load extensions when connecting to an existing instance (`--auto-connect`, `--browserUrl`).
+2. **When connecting to an existing instance (`--auto-connect`, `--browserUrl`, `--wsEndpoint`), use Chrome 149 or later**: earlier versions are not able to load extensions over such a connection. Otherwise, configure the MCP server to launch Chrome.
 
 #### Other Common Errors
 

src/config/category-options.ts

@@ -43,7 +43,7 @@ const categoryOverrides: Record<
   },
   [ToolCategory.EXTENSIONS]: {
     describe:
-      'Set to true to include tools related to extensions. Note: This feature is currently only supported with a pipe connection. autoConnect, browserUrl, and wsEndpoint are not supported with this feature until 149 will be released.',
+      'Set to true to include tools related to extensions. With autoConnect, browserUrl or wsEndpoint, this requires Chrome 149 or later.',
     offByDefault: true,
   },
   [ToolCategory.THIRD_PARTY]: {

src/config/mcp-options.ts

@@ -339,8 +339,6 @@ export const CONFLICTING_ARGS: Array<Array<keyof typeof mcpOptions>> = [
   ['allowUnrestrictedPaths', 'filesystemRoot'],
   ['categoryPwa', 'autoConnect'],
   ['categoryPwa', 'browserUrl', 'wsEndpoint'],
-  ['categoryExtensions', 'autoConnect'],
-  ['categoryExtensions', 'browserUrl', 'wsEndpoint'],
 ];
 
 export const IMPLICATIONS: Array<

tests/cli.test.ts

@@ -1164,36 +1164,16 @@ describe('cli args parsing', () => {
       assert.strictEqual(args.executablePath, '/bin/chrome');
     });
 
-    it('rejects categoryExtensions with autoConnect', async () => {
-      assert.throws(
-        () => parseConfig(['--category-extensions', '--auto-connect']),
-        /Arguments categoryExtensions and autoConnect are mutually exclusive/,
-      );
-    });
-
-    it('rejects categoryExtensions with browserUrl', async () => {
-      assert.throws(
-        () =>
-          parseConfig([
-            '--category-extensions',
-            '--browserUrl',
-            'http://localhost:9222',
-          ]),
-        /Arguments categoryExtensions and browserUrl are mutually exclusive/,
-      );
-    });
-
-    it('rejects categoryExtensions with wsEndpoint', async () => {
-      assert.throws(
-        () =>
-          parseConfig([
-            '--category-extensions',
-            '--wsEndpoint',
-            'ws://localhost:9222',
-          ]),
-        /Arguments categoryExtensions and wsEndpoint are mutually exclusive/,
-      );
-    });
+    for (const connectArgs of [
+      ['--auto-connect'],
+      ['--browserUrl', 'http://localhost:9222'],
+      ['--wsEndpoint', 'ws://localhost:9222'],
+    ]) {
+      it(`allows categoryExtensions with ${connectArgs[0]}`, async () => {
+        const args = parseConfig(['--category-extensions', ...connectArgs]);
+        assert.strictEqual(args.categoryExtensions, true);
+      });
+    }
 
     for (const connectArgs of [
       ['--browserUrl', 'http://localhost:9222'],
@@ -1218,17 +1198,14 @@ describe('cli args parsing', () => {
       });
     }
 
-    it('rejects explicit categoryExtensions with browserUrl in viaCli', async () => {
-      assert.throws(
-        () =>
-          parseConfig([
-            '--viaCli',
-            '--category-extensions',
-            '--browserUrl',
-            'http://localhost:9222',
-          ]),
-        /Arguments categoryExtensions and browserUrl are mutually exclusive/,
-      );
+    it('allows explicit categoryExtensions with browserUrl in viaCli', async () => {
+      const args = parseConfig([
+        '--viaCli',
+        '--category-extensions',
+        '--browserUrl',
+        'http://localhost:9222',
+      ]);
+      assert.strictEqual(args.categoryExtensions, true);
     });
   });