LaunchRepoDefinition
The Chrome DevTools Protocol (CDP) is the interface Chrome exposes for tooling: the same channel the built-in developer tools use, made available to other programs over a local WebSocket. With it a program can open tabs, navigate, read the DOM, dispatch input and take screenshots.
Since Chrome 136 the browser ignores the legacy remote-debugging flags for its default user-data directory, so a driven Chrome needs either the remote-debugging control on the inspect page (Chrome 144+) or a dedicated user-data directory with its own port.
Why it matters for a directory launch
CDP is what turns the browser you are signed in to into something an agent can operate. That is also why it deserves care: a debugging port controls the whole browser, including authenticated pages. Keeping it on the loopback address, never tunnelling it and closing it after a batch are part of the setup, not optional hardening.
How LaunchRepo handles it
BROWSER-SETUP.md offers two modes. A: enable remote debugging on chrome://inspect in Chrome 144+ and let Chrome DevTools MCP auto-connect, approving the connection prompt in the intended window. B: launch a dedicated Chrome with its own user-data directory on 127.0.0.1:9222 and point the MCP server at that URL. Never both at once, never a public port, and the visible tab has to move before a running process counts as access.
See the term in the repository
LaunchRepo is 346 directory playbooks, a product context file and a submission tracker your own agent runs. Pay €99.98 once; use it for every product you own.
See pricing