122 / 168 · 01 Agent Skills for Browser Automation · Evolution: From Selenium to WebDriver BiDi← prev⊞ allnext →☰ Read as one page
16.6Where Vibium Fits
Vibium is BiDi-native from day one. It doesn't abstract over CDP or legacy WebDriver — it speaks BiDi directly.
Traditional stack: Vibium stack:
Test → Playwright → CDP Test → Vibium → BiDi
Playwright → Firefox (same protocol for all browsers)
Playwright → WebKit
Advantages
- No abstraction overhead — BiDi is the protocol, not a compatibility layer
- Future-proof — As BiDi improves, Vibium improves
- Cross-browser potential — When Safari completes BiDi support, Vibium works there
- Simple — One protocol, one implementation, one binary
The Trade-off
- BiDi is newer than CDP — some advanced features (network interception, coverage) are still being standardized
- Chrome's CDP is more feature-rich today — but it's not standardized
- Playwright's CDP-based approach gives you more features now at the cost of vendor dependency