How to Migrate from Playwright to Vibium

Migrating from Playwright to Vibium is mostly a renaming exercise, because Vibium was deliberately designed to Playwright-level developer experience — just on WebDriver BiDi instead of CDP. Both share the same browser → context → page object model, the same auto-waiting on actions, and the same screenshot and navigation patterns. Unlike the Selenium path, there is no drop-in compat shim — you rewrite scripts — but the method map is nearly one-to-one: goto becomes go, locator becomes find, textContent becomes text. The biggest ergonomic upgrade is that Playwright's eight separate getBy* finders collapse into a single find() that takes a CSS string or semantic keywords. In return you get a single Go binary that auto-downloads Chrome, a built-in MCP server for AI agents, and AI-native check() and do() methods. Vibium was created by Jason Huggins, co-creator of Selenium and Appium.

Why migrate from Playwright to Vibium?

The practical motivations are leaner packaging and first-class AI support. Vibium is a single Go binary that auto-downloads Chrome for Testing, removing Node and separate browser installs from the critical path. More importantly, it ships a built-in MCP server, so AI agents drive the browser without bolting on a separate Playwright MCP component.

Playwright remains outstanding for mature multi-language suites and its deep runner ecosystem. Migrate when you want a BiDi-first foundation and AI agents as a first-class use case.

How do I install Vibium?

Install the client and let Vibium manage the browser.

# Python
pip install vibium
 
# JavaScript / TypeScript
npm install vibium

See the install guide for platform notes.

How does Playwright's API map to Vibium?

Most of the migration is mechanical renaming. The table below maps the commands you will touch most often.

The standout difference: Playwright needs getByRole("button").filter({ hasText: "Submit" }) to combine strategies, while Vibium does it in one call — vibe.find(role="button", text="Submit").

What does a converted script look like?

Here is a Playwright login flow and its Vibium equivalent. Vibium's sync API is the default for Python.

# Playwright
from playwright.sync_api import sync_playwright
 
with sync_playwright() as p:
    page = p.chromium.launch().new_page()
    page.goto("https://example.com/login")
    page.get_by_label("Email").fill("admin@example.com")
    page.get_by_label("Password").fill("secret")
    page.get_by_role("button", name="Sign In").click()
    page.screenshot(path="out.png")

# Vibium
from vibium import browser_sync as browser
 
vibe = browser.launch()
vibe.go("https://example.com/login")
vibe.find(label="Email").type("admin@example.com")
vibe.find(label="Password").type("secret")
vibe.find(role="button", text="Sign In").click()
open("out.png", "wb").write(vibe.screenshot())
vibe.quit()

Both auto-wait for elements to be actionable, so you rarely need explicit waits. See the automate-login guide for the full pattern.

What do I gain after migrating?

Beyond the renamed API, Vibium adds features that change how you write automation. The built-in MCP server lets AI agents call Vibium tools directly — set it up in Claude Code. And the AI-native methods let you describe intent instead of selectors:

vibe.do("add the first item to the cart")
result = vibe.check("the cart shows 1 item")
assert result.passed

These sit on top of the deterministic find()/click() API — they plan with AI but execute with Vibium's own commands, so behavior stays inspectable.

What should I watch out for?

A few differences to plan for during migration:

• No compat shim. Unlike Selenium, there is no import-swap bridge for Playwright — you translate scripts using the mapping above.
• Ecosystem maturity. Vibium is new (v1 December 2025), so its test runner, reporter, and plugin ecosystem are smaller than Playwright's. If you depend heavily on Playwright fixtures and reporters, weigh that.
• Language coverage. Vibium ships Python and JS/TS clients today; Playwright additionally offers Java and .NET.

The verdict

Because Vibium was built to Playwright-level DX on BiDi, migration is more renaming than rearchitecting — and the single find() method often makes the result cleaner than the original. The trade is a younger ecosystem in exchange for a leaner single-binary install and genuine AI-native capabilities. If your work is shifting toward agentic browsing, the move is well worth it; if you lean hard on Playwright's runner and reporters, migrate incrementally and keep both during the transition.

Next steps

• Vibium vs Playwright
• Is Vibium faster than Playwright?
• Set up Vibium MCP in Claude Code