Reference
Vibium Glossary
Plain-English definitions of the key Vibium and browser-automation terms.
- Vibium
- An AI-native browser automation tool built on WebDriver BiDi, shipped as a single Go binary with a built-in MCP server. Created by Jason Huggins, co-creator of Selenium and Appium.
- WebDriver BiDi
- The bidirectional successor to the classic WebDriver protocol. It lets a tool both send commands to and receive real-time events from the browser, which powers Vibium's auto-waiting and data collection.
- MCP (Model Context Protocol)
- An open standard that lets AI agents call external tools. Vibium ships a built-in MCP server, so agents like Claude Code and Cursor can drive a real browser without custom integration code.
- Actionability
- Vibium's built-in waiting: before interacting with an element it waits until that element exists, is visible, and is ready — so you rarely need manual sleeps or retry loops.
- Accessibility tree
- The browser's semantic model of a page (roles, names, labels). Vibium can locate elements by these semantics — role, text, label — which is more robust than brittle CSS paths.
- Self-healing locator
- A locator strategy that keeps matching the intended element even when the page's markup shifts, reducing test flakiness as the UI changes.
- Locator
- A selector that identifies an element on the page. Vibium accepts CSS strings and semantic options such as role, text, label, placeholder, and testid.
- find / findAll
- find() returns the first matching element and auto-waits for it to become actionable; findAll() returns all matches immediately as a list (empty if none) without waiting.
- Single Go binary
- Vibium is distributed as one compiled Go executable that manages the browser, removing the dependency tangle and driver-version matching of classic WebDriver setups.
- Headless browser
- A browser that runs without a visible window — common in CI pipelines. Vibium can run Chrome either headless or headed.
- Trace
- A recorded log of a Vibium session used to debug failures by replaying what happened, step by step.
- Sync vs async API
- Vibium offers a synchronous API that reads top-to-bottom with no await, and an asynchronous API for promise-based, concurrent automation.