Chrome CDP

Lightweight Chrome DevTools Protocol CLI. Connects directly via WebSocket — no Puppeteer, works with 100+ tabs, instant connection.

Modes

Default — connect to the user's real Chrome

When invoked without flags, scripts/cdp.mjs auto-discovers the running Chrome instance from the standard profile location (~/Library/Application Support/Google/Chrome/... on macOS, ~/.config/google-chrome/... on Linux, %LOCALAPPDATA%\Google\Chrome\User Data\... on Windows). Remote debugging must be enabled in the user's Chrome (toggle once at chrome://inspect/#remote-debugging).

Use this mode when the user wants to inspect a page they already have open.

--isolated — sandboxed Chrome with a dedicated profile

When the user passes --isolated, drive a separate Chrome instance using --user-data-dir=$HOME/.chrome-debug-profile and --remote-debugging-port=9222. The user's real Chrome profile is untouched (no extensions, no logins, no cookies leak in either direction).

Two-step protocol for every --isolated invocation: