Check Puppeteer's documented WebDriver BiDi support before relying on it, since Chrome and Firefox support differ and some CDP-parity features aren't yet implemented over BiDi
domain: pptr.dev · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Consult Puppeteer's WebDriver BiDi support page to see which browsers it automates via BiDi
Note that Firefox uses BiDi by default when launched through Puppeteer, while Chrome still defaults to CDP — BiDi must be opted into explicitly (protocol: 'webDriverBiDi')
Cross-check the page's explicit list of features 'not supported over WebDriver BiDi' (e.g. direct CDP session access, some emulation methods, coverage, tracing) before depending on them via BiDi
Treat BiDi support as per-feature/per-module rather than a single yes/no per browser, since even supported browsers can lack parity with older CDP-based behavior
Re-verify against the current Puppeteer docs before upgrading, since BiDi coverage is actively evolving
Known gotchas
Puppeteer defaults Chrome automation to CDP even though Chrome itself has BiDi support, purely because Puppeteer's own BiDi implementation hasn't reached full feature parity
'BiDi support' is not one flag per browser — it's granular per API/feature, so a script can hit an unsupported BiDi path even on a browser that's broadly described as BiDi-capable
Safari/WebKit is not part of Puppeteer's supported browser set at all, so this comparison is limited to Chrome and Firefox
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?