fix: Chrome must be fully quit before launching with --remote-debugging-port

Chrome refuses to enable CDP on its default profile when another instance
is running (even with explicit --user-data-dir). The only reliable path:
fully quit Chrome first, then relaunch with the flag.

Updated instructions to emphasize this clearly with verification step.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-03-21 12:32:21 -07:00
parent 65cc48c885
commit 0c207529f5
2 changed files with 16 additions and 16 deletions
+8 -4
View File
@@ -386,12 +386,16 @@ Refs: After 'snapshot', use @e1, @e2... as selectors:
// Handle manual restart needed (Conductor / sandboxed apps)
if (isManualRestart(result)) {
console.log(`\n${result.reason}\n`);
console.log(`To connect, quit ${result.browser.name} and restart it with CDP enabled:\n`);
console.log(`To connect, FULLY QUIT ${result.browser.name} first (no processes running), then relaunch with CDP:\n`);
console.log(` 1. Quit ${result.browser.name} (Cmd+Q)`);
console.log(` 2. Open Terminal and run:`);
console.log(` 2. Wait 3 seconds for all processes to exit`);
console.log(` 3. Verify: pgrep -f "${result.browser.appName}" should return nothing`);
console.log(` 4. Open Terminal and run:`);
console.log(` ${result.command}`);
console.log(` 3. Then run: $B connect ${result.browser.name.toLowerCase()}\n`);
console.log(`Or add this to your shell profile to always launch with CDP:`);
console.log(` 5. Then run: $B connect ${result.browser.name.toLowerCase()}\n`);
console.log(`IMPORTANT: Chrome must be fully quit before step 4. If Chrome is already`);
console.log(`running, it ignores --remote-debugging-port and opens in the existing session.\n`);
console.log(`Pro tip — add to your shell profile to always launch with CDP:`);
console.log(` alias chrome-cdp='${result.command}'\n`);
// Wait and poll — user might restart Chrome while we're printing