123 / 168 · 01 Agent Skills for Browser Automation · Evolution: From Selenium to WebDriver BiDi← prev⊞ allnext →☰ Read as one page
16.7Impact on Test Automation Strategy
For Architects Choosing a Stack
| If You Need... | Choose | Why |
|---|---|---|
| Maximum features now | Playwright (CDP) | Most mature feature set |
| AI agent integration | Playwright CLI + skills | Token-efficient, Microsoft-recommended, same engine |
| Standards purity | BiDi-native tooling (e.g. Vibium) | W3C standard, vendor-neutral — but weigh maturity |
| Cross-browser testing | BiDi-based (long term) | Native cross-browser support |
| Enterprise stability | Selenium 4 (BiDi low-level today) | Existing ecosystem + standards path |
The Convergence
All major tools have converged on BiDi — as of July 2026 this is fact, not forecast:
- Selenium 4 ships low-level BiDi today (~70% of CDP surface, Chrome + Firefox); high-level APIs are the headline for the still-unreleased Selenium 5
- WebdriverIO v9 uses BiDi by default
- Puppeteer has BiDi mode
- Vibium is BiDi-native
Teach BiDi as the present tense of browser automation protocols. The remaining question is timing on Safari completeness and Selenium 5 — not whether BiDi wins.