chrome-cdp
| Version | 2026.170.2101 |
| Repo | superproject |
Chrome DevTools Protocol automation suite exposing CDP on port 9222 via the cdp-proxy service
A CDP automation toolkit layered on /charly-selkies:chrome for
containerized headless streaming desktops. Installs chrome-wrapper
(CDP flags + Windows-UA spoofing + GPU detection), chrome-restart,
browser-open, and cdp-proxy into ~/.local/bin; stages the
chrome-windows browser extension under ~/.local/share; symlinks
google-chrome-stable to the wrapper; and runs cdp-proxy as the
always-restart cdp-proxy service forwarding published port 9222 to
Chrome’s internal 9223. Composes /charly-selkies:chrome-devtools-mcp
for the MCP server. Every fact below is observable: the installed
scripts and their CDP/UA configuration, the staged extension, the
running proxy service, and the HTTP 200 Chrome’s /json/version
endpoint returns through the proxy. Container-only — every feature
assumes a headless context, so it is NOT for target:local installs.
Services
Section titled “Services”cdp-proxy
Acceptance plan
Section titled “Acceptance plan”This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.
| Intent | Step |
|---|---|
run |
mkdir=${HOME}/.local/bin |
run |
mkdir=${HOME}/.local/share/chrome-windows |
run |
mkdir=${HOME}/.config |
run |
copy=chrome-wrapper |
run |
copy=chrome-restart |
run |
copy=browser-open |
run |
copy=cdp-proxy |
run |
copy=chrome-windows/manifest.json |
run |
copy=chrome-windows/rules.json |
run |
copy=chrome-windows/content.js |
run |
link=${HOME}/.local/bin/google-chrome-stable |
check |
the chrome-wrapper launcher is installed and executable in the user’s local bin |
check |
the wrapper enables Chrome’s CDP on the internal debugging port 9223 |
check |
the wrapper spoofs a Windows user-agent for cross-site compatibility |
check |
the cdp-proxy forwarder script is installed and forwards published 9222 to internal 9223 |
check |
the browser-open helper that $BROWSER points at is installed and executable |
check |
the chrome-windows extension manifest is staged under the user’s data dir |
check |
the chrome-windows content script is staged alongside the manifest |
check |
the cdp-proxy service is running under the init system |
check |
Chrome’s CDP /json/version endpoint answers HTTP 200 with a websocket debugger URL through the proxy |
check |
file=${HOME}/.local/bin/browser-open |
check |
file=${HOME}/.local/bin/cdp-proxy |
check |
addr=127.0.0.1:${HOST_PORT:9222} |