CDP
A debugging protocol exposed by the Chrome browser that allows external programs to control the browser or Chromium-based applications programmatically via WebSocket. It supports DOM inspection, JavaScript execution, and network request monitoring, and is also applicable to Electron and other Chromium-based desktop applications.
Core Facts
Google's official Node.js browser automation library Puppeteer is built directly on top of CDP
The Chrome DevTools Protocol (CDP) is a debugging interface exposed by the Chrome browser that allows external programs to control page navigation, execute JavaScript, capture screenshots, and intercept network requests.
Both Playwright and Puppeteer communicate with browsers via CDP (Chrome DevTools Protocol) or similar protocols
Timeline (last 90 days)
CDP (Chrome DevTools Protocol) is the low-level control protocol provided by Chrome/Chromium, and automation libraries such as Puppeteer and Playwright are all built on top of it.
Mac Computer Use's CDP Targets feature can connect to embedded web pages to read page structure, supporting the operation of Chromium-based desktop applications.
Previously, syncing the results needed for advertising to the Meta advertising platform required additional ETL pipelines or third-party CDP (Customer Data Platform) tools.
Automation frameworks such as Playwright and Puppeteer both rely on CDP at the underlying level to interact with the browser.
Firecrawl 2.11 provides a CDP URL (Chrome DevTools Protocol address), allowing a local Playwright instance to connect to a Firecrawl cloud browser.
After launching Chrome with the --remote-debugging-port parameter, Playwright or Puppeteer can attach to an already-running instance using the connect method, enabling login once and reuse multiple times.
Cloud-based stateful browser platforms such as Browserbase and Steel host the browser infrastructure and expose CDP WebSocket endpoints for Agent connections.
The execution agent, named Cotine (abbreviated as Crum), runs on CDP debug port 9222, is a compiled debug version of the application, and has two modes: task mode and command mode.
Electron applications are essentially desktop programs rendered with Chromium, and therefore natively support launching a CDP debug port with the --remote-debugging-port parameter.
Chrome DevTools MCP wraps the CDP protocol into an MCP toolset, allowing the Agent to perform operations such as clicking buttons, reading page content, and executing scripts via standard tool calls, without having to manually write low-level WebSocket communication.
9 more timeline events
All Facts (20)
Google's official Node.js browser automation library Puppeteer is built directly on top of CDP
80%VerifiedThe Chrome DevTools Protocol (CDP) is a debugging interface exposed by the Chrome browser that allows external programs to control page navigation, execute JavaScript, capture screenshots, and intercept network requests.
65%VerifiedBoth Playwright and Puppeteer communicate with browsers via CDP (Chrome DevTools Protocol) or similar protocols
65%VerifiedAutomated testing frameworks such as Puppeteer and Playwright are both built on CDP.
65%Partially VerifiedBrowser Use supports connecting to existing browser instances via CDP (Chrome DevTools Protocol) or WebSocket, reusing existing login states and cookies.
100%UnverifiedCDP（Chromium DevTools Protocol）是Google为Chromium内核浏览器设计的底层调试与自动化协议，基于WebSocket通信
95%UnverifiedCDP是Google Chrome暴露的底层调试接口，允许外部程序通过WebSocket与浏览器内核直接通信
95%UnverifiedBrowser Use 早期版本基于 Playwright 实现浏览器控制，最新版本已切换到 CDP（Chrome DevTools Protocol）
90%Unverified传统浏览器自动化工具基于WebDriver协议或CDP（Chrome DevTools Protocol）驱动浏览器，所有操作路径必须由开发者预先硬编码
90%Unverified在Windows上开启Chrome调试端口9222后，WSL或远程Linux可通过CDP协议连接并复用已登录的浏览器环境
90%UnverifiedPlaywright 虽然也使用 CDP 与 Chromium 通信，但在其上增加了一层自己的抽象协议和进程管理机制
85%UnverifiedCDP (Chrome DevTools Protocol) is the low-level control protocol provided by Chrome/Chromium, and automation libraries such as Puppeteer and Playwright are all built on top of it.
50%UnverifiedMac Computer Use's CDP Targets feature can connect to embedded web pages to read page structure, supporting the operation of Chromium-based desktop applications.
50%UnverifiedPreviously, syncing the results needed for advertising to the Meta advertising platform required additional ETL pipelines or third-party CDP (Customer Data Platform) tools.
50%UnverifiedAutomation frameworks such as Playwright and Puppeteer both rely on CDP at the underlying level to interact with the browser.
50%UnverifiedAfter launching Chrome with the --remote-debugging-port parameter, Playwright or Puppeteer can attach to an already-running instance using the connect method, enabling login once and reuse multiple times.
50%UnverifiedCloud-based stateful browser platforms such as Browserbase and Steel host the browser infrastructure and expose CDP WebSocket endpoints for Agent connections.
50%UnverifiedElectron applications are essentially desktop programs rendered with Chromium, and therefore natively support launching a CDP debug port with the --remote-debugging-port parameter.
50%UnverifiedChrome DevTools MCP wraps the CDP protocol into an MCP toolset, allowing the Agent to perform operations such as clicking buttons, reading page content, and executing scripts via standard tool calls, without having to manually write low-level WebSocket communication.
50%UnverifiedRamp built a customer data platform (CDP) in-house that integrates CRM data, product data, enrichment data, web data, and purchase signals
50%