Skip to content

Conversation

@arnonuem
Copy link

• Fix CLI silently swallowing launch errors when using --headed/--proxy flags
by checking response.success, not just network errors
• Fix isLaunched() returning true for disconnected browsers by checking
browser.isConnected() and cleaning up stale state
• Add browser.on('disconnected') handler to proactively reset state when
browser crashes or is closed externally

Before: Closing browser window caused "Browser not launched. Call launch first" error on next command, requiring manual close to recover.

After: Browser state is properly tracked; auto-relaunch works reliably.

Fixes zombie daemon state issue on Windows (and likely other platforms).

@vercel
Copy link
Contributor

vercel bot commented Jan 20, 2026

@arnonuem is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

• Fix CLI silently swallowing launch errors when using --headed/--proxy flags
  by checking response.success, not just network errors
• Fix isLaunched() returning true for disconnected browsers by checking
  browser.isConnected() and cleaning up stale state
• Add browser.on('disconnected') handler to proactively reset state when
  browser crashes or is closed externally

Before: Closing browser window caused "Browser not launched. Call launch first"
error on next command, requiring manual close to recover.

After: Browser state is properly tracked; auto-relaunch works reliably.

Fixes zombie daemon state issue on Windows (and likely other platforms).
@arnonuem arnonuem force-pushed the fix__browser-launch-reliability branch from 97c806a to 6c69928 Compare January 20, 2026 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant