chrome-cdp-setuplisted

# Chrome CDP Setup (macOS Dock launcher) Makes the Dock's Chrome icon launch Chrome with `--remote-debugging-port` so any local agent can connect over CDP. Chrome 136+ silently ignores that flag on the default profile directory, so the launcher points Chrome at a one-time APFS clone of the real profile — all logins, bookmarks, and extensions carry over at near-zero disk cost. Scripts live in this skill's `scripts/` dir; run them with absolute paths (`~/.claude/skills/chrome-cdp-setup/scripts/...`). ## Quick start ```bash scripts/setup_chrome_cdp.sh # full setup (default port 9222) scripts/verify_cdp.sh # endpoint + loopback + flags health check uv run --with playwright python scripts/cdp_agent_test.py # external-agent smoke test ``` ## Setup workflow 1. Preflight: confirm `/Applications/Google Chrome.app` exists and `/Applications` is writable; note profile size with `du -sh ~/Library/Application\ Support/Google/Chrome`. 2. Run `scripts/setup_chrome_cdp.sh [port]`. It is idempotent and: - quits Chrome cleanly (session restores on relaunch) - clones `~/Library/Application Support/Google/Chrome` → `Chrome-CDP` (`cp -Rc`; skipped if the clone already exists) - builds `/Applications/Google Chrome CDP.app` (Chrome's own icon, ad-hoc signed) - swaps the Dock's Chrome tile for the wrapper (Dock prefs backed up first) and restarts the Dock - launches the wrapper and waits for `http://127.0.0.1:<port>/json/version` 3.