browse env local auto-discovers debuggable Chrome instances
Introduced 2026-03-31 · score 0.97
HOW TO USE IT
When automating in an existing Chrome instance with remote debugging enabled, run `browse env local` to auto-discover and attach; use `--isolated` to launch an isolated browser, a positional CDP target to select a target, or `--ws <port>` with a bare port number. If no debuggable Chrome is found, it falls back to an isolated launch.
WHY THIS HELPS
Run local browser automation against an existing Chrome instance with remote debugging enabled.
BEFORE THIS CHANGE
Run `browse env local`, which always launches an isolated browser.
REQUIREMENTS AND LIMITATIONS
- Version: 0.4.0
- Auto-discovery attaches only to Chrome instances with remote debugging enabled.
- When no debuggable Chrome is found, the command falls back to an isolated launch.
FIRST-PARTY EVIDENCE
Check the installed version and the source before using it. Entry JSON