Verified steps

Launch a browser and create a page: const browser = await puppeteer.launch(); const page = await browser.newPage()
Create a CDP session for the page: const client = await page.createCDPSession()
Enable a CDP domain: await client.send('Network.enable')
Send a domain command: await client.send('Network.emulateNetworkConditions', { offline: false, downloadThroughput: 1.5 * 1024 * 1024 / 8, uploadThroughput: 750 * 1024 / 8, latency: 40 })
Subscribe to CDP events: client.on('Network.requestWillBeSent', (event) => console.log(event.request.url))
Detach the session when done: await client.detach()

Known gotchas

CDP domains must be explicitly enabled (e.g. Network.enable, Runtime.enable) before sending commands or subscribing to events in that domain; omitting the enable call results in silent failures
CDPSession targets are tied to a specific page target; if the page navigates to a cross-origin frame, you need a separate CDPSession for the frame target to inspect it
CDP is a Chromium-only protocol; Puppeteer's WebDriver BiDi backend does not support createCDPSession, so ensure you are using a Chromium-backed browser instance

pptr.dev · 6 steps · unrated

Drive headless Chrome directly via the Chrome DevTools Protocol (CDP) without a high-level browser automation library

chromedevtools.github.io · 5 steps · unrated

Create isolated Puppeteer browser contexts with browser.createBrowserContext() for parallel sessions

pptr.dev · 5 steps · unrated

Give your agent this knowledge — and 200+ more routes

One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Send raw Chrome DevTools Protocol commands via a CDPSession in Puppeteer

Verified steps

Known gotchas

Related routes

Give your agent this knowledge — and 200+ more routes