Case Study: Vibium — The AI-Native Bet

Updated Jul 2026

Why Study a Tool You Probably Won't Deploy

Vibium is Jason Huggins' — the creator of Selenium (2004) — attempt to rebuild browser automation from scratch for the agent era. As of July 2026 it has shipped V1 (June 1, 2026, calver 26.5.31 on PyPI/npm, Apache 2.0) but shows no meaningful production adoption: no enterprise case studies, no CI-platform integrations, coverage limited to founder interviews and QA-influencer blogs.

So why keep it in this guide? Two reasons. First, its design choices are genuinely instructive — several of them anticipate where the whole field went (Playwright's CLI, disk-first state, skills over MCP). Second, "what do you think of Vibium?" is a live interview question in 2026, and the credible answer is neither hype nor dismissal — it's the analysis below.

The Design in Five Ideas

1. A single Go binary as a BiDi proxy. One ~10MB binary launches Chrome, speaks W3C WebDriver BiDi over WebSocket, and exposes ~22 CLI commands (navigate, click, type, find-all, screenshot, tab management…). No driver zoo, no language bindings required.

2. A skill, not a protocol. The vibe-check SKILL.md teaches any coding agent the full command set for a few hundred tokens — the same skills thesis this module opened with, and the same conclusion Microsoft later reached with playwright-cli install --skills.

3. Server-side actionability. The five Playwright-pioneered checks (visible, stable, receives-events, enabled, editable) run in a 100ms polling loop with a 30s timeout — but implemented once, in Go, server-side, so every client (CLI, JS, Python, MCP) gets identical behavior instead of each client library reimplementing them. Failures name the failing check ("obscured by div.modal-overlay"). This is arguably a cleaner architecture than Playwright's per-client implementation, and it's a great interview example of the "implement once at the chokepoint" principle.

4. Daemon vs oneshot. A background daemon keeps Chrome hot (~100ms per command vs ~2s cold start) for interactive agent sessions; oneshot mode gives fresh-browser isolation for CI. The daemon work surfaced a real systems problem — Chrome's 8–12 child processes get orphaned to PID 1 when the driver dies — solved with three-phase cleanup (graceful session delete → recursive tree kill → orphan sweep). Worth knowing as a systems-thinking story regardless of the tool.

5. Sense → Think → Act roadmap. V1 shipped only "Act" (the Clicker) with an MCP server built into the binary. The more ambitious pieces — Retina (a Chrome extension observing everything) and Cortex (SQLite + embeddings "app map" memory so the agent remembers your application between sessions) — remain roadmap. The persistent-app-memory idea is the one to watch: nobody has shipped it well yet, and whoever does changes the economics of exploratory agent testing.

Honest Scorecard (July 2026)

What Actually Happened to Its Thesis

This is the interesting part. Vibium's January 2026 pitch — CLI skills beat MCP on token economics — won the argument while the tool itself stayed niche. Microsoft shipped @playwright/cli with a --skills flag and now recommends CLI over its own MCP server for coding agents (~4x token savings). The idea propagated faster than the implementation. That happens constantly in this industry, and being able to narrate a live example of it is worth more in an architect interview than fluency in any single tool.

Interview Talking Point

"Vibium is Jason Huggins' AI-native rebuild of browser automation — a Go binary speaking WebDriver BiDi, driven by CLI skills, with actionability checks done server-side so every client behaves identically. It shipped V1 in June 2026 but hasn't shown production adoption, so I wouldn't build a framework on it today. What I'd take from it is the architecture: its skills-over-MCP token argument was validated when Microsoft's own Playwright CLI took the same path, and its planned Cortex 'app memory' points at the next real frontier — agents that remember the application between sessions. I track it; I don't bet on it yet."