fix: mark categoryExtensions flag mutually exclusive with autoConnect

Author: nroscino

src/bin/chrome-devtools-mcp-cli-options.ts

@@ -12,7 +12,7 @@ export const cliOptions = {
     type: 'boolean',
     description:
       'If specified, automatically connects to a browser (Chrome 144+) running locally from the user data directory identified by the channel param (default channel is stable). Requires the remoted debugging server to be started in the Chrome instance via chrome://inspect/#remote-debugging.',
-    conflicts: ['isolated', 'executablePath'],
+    conflicts: ['isolated', 'executablePath', 'categoryExtensions'],
     default: false,
     coerce: (value: boolean | undefined) => {
       if (!value) {
@@ -26,7 +26,7 @@ export const cliOptions = {
     description:
       'Connect to a running, debuggable Chrome instance (e.g. `http://127.0.0.1:9222`). For more details see: https://github.com/ChromeDevTools/chrome-devtools-mcp#connecting-to-a-running-chrome-instance.',
     alias: 'u',
-    conflicts: 'wsEndpoint',
+    conflicts: ['wsEndpoint', 'categoryExtensions'],
     coerce: (url: string | undefined) => {
       if (!url) {
         return;
@@ -44,7 +44,7 @@ export const cliOptions = {
     description:
       'WebSocket endpoint to connect to a running Chrome instance (e.g., ws://127.0.0.1:9222/devtools/browser/<id>). Alternative to --browserUrl.',
     alias: 'w',
-    conflicts: 'browserUrl',
+    conflicts: ['browserUrl', 'categoryExtensions'],
     coerce: (url: string | undefined) => {
       if (!url) {
         return;
@@ -213,7 +213,9 @@ export const cliOptions = {
     type: 'boolean',
     default: false,
     hidden: true,
-    describe: 'Set to false to exclude tools related to extensions.',
+    conflicts: ['browserUrl', 'autoConnect', 'wsEndpoint'],
+    describe:
+      'Set to true to include tools related to extensions. Note: This feature is only supported with a pipe connection. autoConnect is not supported.',
   },
   performanceCrux: {
     type: 'boolean',