chrome-cdp is a tool that gives AI agents direct access to a live Chrome browser session through the Chrome DevTools Protocol.
The tool solves the problem of AI agents needing to interact with authenticated, stateful browser sessions. Rather than launching a fresh isolated browser instance, it connects directly to Chrome's remote debugging WebSocket to access tabs you already have open with their current login state and page content. It spawns a lightweight background daemon per tab that holds the debugging session open, so the browser's permission modal appears only once per tab and subsequent commands reuse that persistent connection.
Teams should adopt this tool when they need agents to work with logged-in accounts, internal tools, or mid-workflow page states that would be lost in a fresh browser launch. It works out of the box with any Chrome installation on macOS, Linux, or Windows—just enable remote debugging at chrome://inspect/#remote-debugging and point your agent to the skill directory. The only runtime dependency is Node.js 22 or later. The README contrasts it with chrome-devtools-mcp, which reconnects on every command and causes the browser's permission modal to reappear repeatedly; chrome-cdp's persistent daemon approach handles over 100 open tabs reliably where Puppeteer-based tools often time out during target enumeration.
Development activity shows consistent maintenance with regular commits addressing edge cases and user-reported issues. The project maintains clear documentation of its design decisions and actively responds to comparisons with alternative approaches. Commits demonstrate attention to cross-platform compatibility and daemon lifecycle management. The maintainer has documented known limitations and provides environment variable configuration for non-standard browser setups.
