| title | FAQ |
|---|
Vibium targets AI agents first and humans second. Its surface area is
small and verb-shaped (go, map, click, fill), its element references
are short and human-readable (@e1), and it favors semantic locators
(text, label, placeholder, role) over CSS selectors. The result is a tool an
LLM can use correctly with very little prompting.
Under the hood it speaks W3C WebDriver BiDi, the same standards-track protocol the wider browser-automation ecosystem is moving toward.
Vibium ships with its own managed Google Chrome for Testing build, downloaded automatically on first use. Future browser support will follow as more browsers ship BiDi.
No. Vibium is one ~10 MB binary. There is no chromedriver, no geckodriver,
no profile directory you have to maintain.
No. Every command works through npx:
npx -y vibium go https://example.com
npx -y vibium screenshot -o page.png
npx -y vibium textThis is convenient for CI jobs, throwaway scripts, sandboxes, or any host where you'd rather not install software globally. See Installation for details.
Yes. The browser will run without a visible window on hosts without a display.
Capture commands (screenshot, text, pdf) work the same way as on a
desktop.
Yes — see Client Libraries. All three wrap the same binary, so behavior is identical across languages.
Register Vibium as an MCP server. See MCP Server Integration.
CSS selectors are brittle: a refactor of class names breaks all your tests.
They are also hard for an LLM to produce reliably. Semantic locators
(find text "Sign in", find label "Email", find role button) describe
what a human would describe, which is also what an LLM tends to produce
naturally.
vibium eval is still available when you genuinely need a CSS or XPath
selector for something the semantic API can't express.
Apache 2.0.
The bundled browser and any cached state live in Vibium's data directory. Removing that directory wipes Vibium's local state without affecting your system Chrome.