A new open-source tool called chrome-cdp-skill enables AI agents to interact directly with active Chrome browser sessions by connecting to tabs users already have open. Created by Petr Baudis (@pasky on GitHub), the tool allows agents to access logged-in accounts and see real page states without launching new browser instances. The repository has garnered 686 stars on GitHub as of March 13, 2026.
Direct WebSocket Connection Eliminates Puppeteer Overhead
Chrome-cdp-skill connects directly to Chrome's remote debugging WebSocket protocol, bypassing intermediary frameworks like Puppeteer entirely. When an AI agent first accesses a tab, a background daemon spawns to maintain the persistent connection. Chrome's permission modal appears once per tab during initial access; subsequent commands reuse the same daemon silently. These daemons automatically close after 20 minutes of inactivity, keeping resource usage minimal.
Tool Handles 100+ Tabs Where Puppeteer-Based Solutions Timeout
The architecture delivers significant advantages over competing solutions like chrome-devtools-mcp. By avoiding reconnection on every command, chrome-cdp-skill prevents repeated permission prompts and timeout issues. The creators claim it reliably handles 100+ open tabs simultaneously, a scenario where tools built on Puppeteer frequently timeout or fail.
To use the tool, developers need to enable Chrome's remote debugging feature and have Node.js 22+ installed. The tool works with any Chrome installation after enabling the debugging protocol. Contributions from fredheir have helped expand the tool's capabilities since its initial release.
Key Takeaways
- Chrome-cdp-skill connects AI agents directly to active Chrome tabs via WebSocket, eliminating the need for Puppeteer or new browser instances
- The tool uses persistent daemons that spawn once per tab and automatically close after 20 minutes of inactivity
- It handles 100+ open tabs reliably where Puppeteer-based solutions often timeout
- The repository has received 686 GitHub stars as of March 13, 2026
- Requires Node.js 22+ and Chrome with remote debugging enabled