Updates & roadmap

Highlights of where Vibium is and where it's headed. For the authoritative, always-current list, follow the GitHub releases.

v26.8.21

Latest release at time of writing

12

Releases shipped

2.9k★

GitHub stars and growing

Release highlights

What's landed

On mainUnreleased · as of Sep 24, 2026
  • Verify: an AI-backed runtime that checks whether an agent's run actually did what it claimed — Run and Check workflows, shared AI providers, readiness diagnostics, and recorder redaction, exposed across the SDKs.
  • Classic WebDriver connect: POST /session plus webSocketUrl brings cloud grids onto the standard connect path — Sauce Labs, BrowserStack, Kernel, TestingBot and LambdaTest (TestMu) guides, each live-verified.
  • Exposed functions: pages can call back into the JS, Python and Java clients.
  • Agent isolated pages: agents can open pages with their own cookies and storage instead of sharing one current tab.
  • Self-hosted / cloud-hosted deploy kits: browser-box recipes for AWS, Hetzner, GCP and Fly.io.
  • vibium setup: an interactive wizard that picks an AI provider and model, stores keys in ai.env (skipped if world-readable), installs agent skills for the agents it detects, and ends by suggesting a first command.
  • More AI providers for Verify: native xAI (reusing a signed-in Grok CLI session), GEMINI_API_KEY for Google, and recordings that redact Anthropic and Google keys.
  • Flag rename: the AI endpoint flag is now --ai-base-url; on run and check, --base-url names the site under test.

Merged but not yet in a tagged release — build from source to try these.

v26.8.21Latest release · Aug 22, 2026
  • Firefox support: --engine firefox drives Firefox end to end, auto-installed and checksum-verified alongside Chrome, with full network, dialog, console and navigation event coverage.
  • Video recording: recording.start gains a video track on every surface, captured natively over BiDi screencast — one record.zip now carries screenshots, snapshots and the WebM together.
  • Java client parity: one-shot capture APIs, WebSocket monitoring, request post data, screencast, and exceptions that carry caller frames.
  • Concurrency: named CLI sessions (--session) stop scripts colliding on shared hosts, the pipe transport no longer wedges on a stalled reader, and the CLI recovers when the browser crashes externally.
  • Browser control: custom Chrome flags via VIBIUM_CHROME_ARGS, and a clear message instead of a crash when Chrome will not start as root.
  • Packaging: downloaded browsers are checksum-verified, and nightly prereleases now publish automatically from the newest CI-green commit on main.
Core capabilities
  • Single ~10 MB binary with automatic browser download.
  • Chrome and Firefox as first-class engines, with native video recording over BiDi screencast.
  • Built-in MCP server as a first-class interface.
  • Semantic element finding by text, label, placeholder and ARIA role.
  • Actionability system to prevent "element not interactable" errors.
Client libraries
  • JavaScript/TypeScript, Python and Java client libraries with sync & async APIs.
  • vibe-check agent skill for one-command setup.
Foundations
  • Built on the open WebDriver BiDi standard.
  • CLI with go, map, find, click, fill, screenshot and more.
  • Apache 2.0 license.
Version numbers and dates here are a snapshot. The GitHub Releases page is the source of truth — check it for the exact current version and changelog.
Roadmap

On the horizon

🗂️

Records

Help agents remember pages and paths between sessions, with an early UI prototype to browse and edit that memory.

🎯

Find an element by description

Ask for an element in plain language — vibe.find("the blue submit button") — and get one back.

🌐

More browsers

Edge and Safari support, plus video recording in more browsers as their protocol support allows.

☁️

Easier CI and cloud setup

Container images and recipes for CI, then hosted Run and Check, cloud browsers for those operations, and PR integration.

🔷

A .NET client

Official C# support, building on an existing community implementation.

See the official ROADMAP.md for details.

Stay current

Follow along