Launch Google Chrome with Chrome DevTools Protocol (CDP) remote debugging enabled.
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://raw.githubusercontent.com/AnswerDotAI/cdpchrome/main/install-mac.sh | bash
This 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:
curl -fsSL https://raw.githubusercontent.com/AnswerDotAI/cdpchrome/main/cdpchrome.sh -o ~/.local/bin/cdpchrome && chmod +x ~/.local/bin/cdpchrome
Or download from Releases and run the install script for desktop integration (icon + app launcher):
tar xzf cdpchrome-linux-amd64.tar.gz
./install.sh # installs to ~/.local by default
./install.sh /usr/local # or system-wide
Windows (PowerShell as admin):
irm https://raw.githubusercontent.com/AnswerDotAI/cdpchrome/main/install-windows.ps1 | iex
This finds Chrome, downloads the icon, and creates a Start Menu shortcut.
On Mac, run ‘CDP Chrome’ from Spotlight or any normal Mac launching approach. On Windows, use the Start Menu shortcut. On any platform through the terminal:
cdpchrome # launch Chrome with CDP on port 9222
cdpchrome https://example.com # open a specific URL
Then 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.