fix(windows): work around Chrome not reporting reasons for crash

Author: OrKoN

src/browser.ts

@@ -83,11 +83,7 @@ export async function launch(options: McpLaunchOptions): Promise<Browser> {
     });
   }
 
-  const args: LaunchOptions['args'] = [
-    '--remote-debugging-pipe',
-    '--no-first-run',
-    '--hide-crash-restore-bubble',
-  ];
+  const args: LaunchOptions['args'] = ['--hide-crash-restore-bubble'];
   if (customDevTools) {
     args.push(`--custom-devtools-frontend=file://${customDevTools}`);
   }
@@ -111,11 +107,11 @@ export async function launch(options: McpLaunchOptions): Promise<Browser> {
       args,
     });
   } catch (error) {
-    // TODO: check browser logs for `Failed to create a ProcessSingleton for
-    // your profile directory` instead.
     if (
       userDataDir &&
-      (error as Error).message.includes('The browser is already running')
+      ((error as Error).message.includes('The browser is already running') ||
+        (error as Error).message.includes('Target closed') ||
+        (error as Error).message.includes('Connection closed'))
     ) {
       throw new Error(
         `The browser is already running for ${userDataDir}. Use --isolated to run multiple browser instances.`,