Understand the current state of WebDriver BiDi and decide when to use it over CDP or WebDriver Classic

Steps

1. Understand the positioning: WebDriver BiDi is a W3C standard bidirectional protocol designed to bring CDP-like capabilities (event subscriptions, script evaluation, network interception) to all browsers under one API, replacing per-vendor protocols.
2. Check browser support before committing — as of 2025, Chromium-based browsers and Firefox have meaningful BiDi support, but WebKit/Safari support is still catching up. Verify the feature matrix on the WebDriver BiDi spec repository before relying on a specific command.
3. Use BiDi when you need a standards-based cross-browser automation protocol and your target browsers support the features you need — particularly for new tooling built to be browser-agnostic.
4. Prefer CDP directly (via Puppeteer or raw WebSocket) when you need Chromium-specific features not yet in the BiDi spec, or when you need the most complete and stable implementation today.
5. In Playwright, BiDi is used internally for Firefox; for end users the Playwright API abstracts the protocol — you do not write BiDi commands directly unless building tooling at the driver layer.