Launch Google Chrome with Chrome DevTools Protocol (CDP) remote debugging enabled. A standalone binary that works from the command line, Finder, Explorer, or Linux desktop launchers.
Chrome is launched with --remote-debugging-port=9222 and a dedicated user data directory so it doesn't interfere with your normal Chrome profile.
macOS:
curl -fsSL https://github.com/ghraw/AnswerDotAI/cdpchrome/main/install-mac.sh | bashThis downloads the latest release and installs CDP Chrome.app to Applications.
Alternatively, download from Releases, unzip, and drag to Applications. If you install this way, macOS will block the app on first launch because it's not signed — go to System Settings > Privacy & Security and click Open Anyway.
Linux: Download the latest release from Releases. Extract the tarball and run the install script:
tar xzf cdpchrome-linux-amd64.tar.gz
./install.sh # installs to ~/.local by default
./install.sh /usr/local # or system-wideWindows: Download the latest release for your platform from Releases. Unzip and run cdpchrome.exe.
On Mac, run 'CDP Chrome' from Spotlight or any normal Mac launching approach. Or on any platform through the terminal:
cdpchrome # launch Chrome with CDP on port 9222
cdpchrome https://example.com # open a specific URLThen connect to CDP at http://localhost:9222.
A separate profile is used so CDP Chrome doesn't conflict with your regular Chrome:
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/ChromeDebug |
| Linux | ~/.config/chrome-debug |
| Windows | %LOCALAPPDATA%\ChromeDebug |
See DEV.md for building from source, releasing, and internals.