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+ ignores that flag on the default profile directory, and the Chrome 144+ `chrome://inspect` toggle that does work there makes a human approve every connection — 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, the flags take precedence over the toggle, and nothing ever prompts. Scripts live in this skill's `scripts/` dir; run them with absolute paths (`~/.claude/skills/chrome-cdp-setup/scripts/...`). ## Which route | Need | Route | |---|---| | Unattended agent loop, headless, CI, several tools sharing one browser | **This skill**: flags + a separate `--user-data-dir`, launched from the Dock wrapper. No prompts. | | Real default profile, human at the keyboard, occasional | `chrome://inspect/#remote-debugging` toggle, then `PLAYWRIGHT_MCP_CDP_TIMEOUT=0 playwright-cli attach --cdp=chrome`; the human clicks Allow once per connection. See REFERENCE.md "Approval mode". | | Real default profile, one tab, no Chrome prompt | `playwright-cli attach --extension=chrome` (Playwright extension). Per-tab access; its own approval popup takes a shared token via `PLAYWRIGHT_MCP_EXTENSION_TOKEN`. | | Real default profile, whole browser, no prompt | Not possible in Chrome 136+. The profile clone is the closest thing. | ## Quick