cdp
Also expose a Chrome DevTools Protocol endpoint (cdpUrl).
Use it for: Puppeteer users and tools that speak raw CDP (Lighthouse, custom DevTools clients), or connecting with Playwright's connectOverCDP to reach Chromium-only features like network throttling and performance traces.
Browsers: Google Chrome, Microsoft Edge, Brave, Opera, Yandex Browser, Chromium.
Details
- Type:
boolean - Default: false
- Example:
{"cdp":true}
The launch response then carries cdpUrl next to wsUrl: a browser-level CDP WebSocket for Puppeteer (puppeteer.connect({ browserWSEndpoint: cdpUrl, headers })), Playwright's connectOverCDP(cdpUrl, { headers }) in any language and version, or any raw CDP client (key in the x-api-key header or ?api_key=).
Same session, proxy and limits. You can connect to wsUrl and cdpUrl at once, but closing either ends the session. Not on Patchright and Rebrowser (their stealth lives in the Playwright layer CDP bypasses), Whale, Camoufox, Firefox or WebKit.
Used in
- Case 42: Puppeteer on real Google Chrome: cdpUrl, raw CDP and request interception
- Case 43: Can a page tell your automation client is listening? CDP and the console
- Case 26: Same Chrome, two doors: Playwright's protocol (wsUrl) or CDP (cdpUrl)
- Chrome over CDP (connectOverCDP or Puppeteer)
- Microsoft Edge over CDP (Puppeteer or connectOverCDP)
- Brave over CDP (Puppeteer or connectOverCDP)
- Opera over CDP (Puppeteer or connectOverCDP)
- Yandex Browser over CDP (Puppeteer or connectOverCDP)
- Microsoft Edge over CDP that survives a disconnect
- Headful Opera over CDP that survives a disconnect
All options: launch options.