Vibium
Concepts & Internals
WebDriver BiDi, the accessibility tree, actionability, self-healing locators, tracing.
WebDriver BiDi vs CDP: What's the Difference?
WebDriver BiDi vs CDP: both are bidirectional protocols, but BiDi is a cross-browser W3C standard while CDP is Chrome-specific and vendor-controlled.
4 min read→Concepts & InternalsEvent-Driven Browser Automation with Vibium
Event-driven browser automation with Vibium uses WebDriver BiDi's pushed events for auto-waiting, console capture, and reliable scripts without sleeps.
4 min read→Concepts & InternalsHow Vibium's Actionability (Auto-Wait) Works
Vibium's actionability auto-wait runs checks (visible, stable, receives events, enabled, editable) server-side in Go before each action — skip sleeps.
4 min read→Concepts & InternalsSelf-Healing Locators in Vibium, Explained
Vibium has no bolt-on self-healing locator engine — it earns resilience via semantic selectors, accessibility-tree finding, pickBest, and auto-wait.
4 min read→Concepts & InternalsSync vs Async in Vibium: How It Works Under the Hood
Sync vs async in Vibium under the hood: both clients call the same Go binary over a local WebSocket, so blocking and awaiting share one automation engine.
4 min read→Concepts & InternalsFinding Elements with the Accessibility Tree in Vibium
Use Vibium's a11y_tree() to inspect a page the way assistive tech sees it, then find and click elements by role and name — resilient, human-like selectors.
4 min read→Concepts & InternalsInside Vibium's Single Go Binary Architecture
Vibium ships as one ~10MB Go binary bundling browser management, a WebDriver BiDi proxy, auto-wait, and an MCP server. Here's the architecture.
5 min read→Concepts & InternalsHow Vibium Manages the Browser Process Lifecycle
How Vibium manages the browser process lifecycle: launching Chrome, the process tree it spawns, and how it cleans up so you don't leave zombie processes.
4 min read→Concepts & InternalsUnderstanding the Vibium Trace Format
The Vibium trace format is a zip of newline-delimited JSON — a timeline, a network HAR stream, and SHA1-named resources — viewable at trace.vibium.dev.
4 min read→Concepts & InternalsWebDriver BiDi vs Classic WebDriver
WebDriver BiDi vs Classic WebDriver, the protocol behind Vibium: BiDi is bidirectional over WebSockets with pushed events; classic is one-way HTTP.
4 min read→Concepts & InternalsWhat Is WebDriver BiDi?
WebDriver BiDi is the W3C standard for bidirectional browser automation that powers Vibium. Here's what it is, where it came from, and why it matters.
3 min read→Concepts & InternalsWhy Vibium Chose WebDriver BiDi
Why Vibium chose WebDriver BiDi: a vendor-neutral W3C standard with real-time events, cross-browser reach, and stability proprietary protocols lack.
4 min read→