Vibium

Vibium is a brand-new browser automation framework for AI agents that is built on WebDriver BiDi, a W3C standard. As of v26.3.9, any agent can now use Vibium to connect to Kernel cloud browsers to navigate pages, fill forms, click buttons, and take screenshots. We’re really excited to keep working with Jason Huggins and to keep supporting open web standards.

Adding Kernel to existing Vibium implementations

If you already have a Vibium implementation, you can switch to using Kernel’s cloud browsers by creating a Kernel browser session and connecting Vibium to the returned webdriver_ws_url.

1. Install Kernel and Vibium

CLI

npm install -g @onkernel/cli vibium

2. Create a Kernel browser

CLI

browser_json="$(kernel browsers create -o json)"
session_id="$(printf '%s' "$browser_json" | jq -r '.session_id')"
webdriver_ws_url="$(printf '%s' "$browser_json" | jq -r '.webdriver_ws_url')"

3. Connect Vibium to your Kernel browser

CLI

vibium start "$webdriver_ws_url"

4. Use your Vibium automation

Use Vibium’s page methods with the Kernel-powered browser:

CLI

vibium go https://example.com
vibium title        # "Example Domain"
vibium text h1      # "Example Domain"

5. Clean up

When you’re done, close Vibium and delete the Kernel browser session:

CLI

vibium stop
kernel browsers delete "$session_id"

Using Vibium CLI with Kernel

The CLI can connect directly to the Kernel browser’s WebDriver BiDi endpoint:

export KERNEL_API_KEY=<your kernel api key>

browser_json="$(kernel browsers create -o json)"
session_id="$(printf '%s' "$browser_json" | jq -r '.session_id')"
webdriver_ws_url="$(printf '%s' "$browser_json" | jq -r '.webdriver_ws_url')"

vibium start "$webdriver_ws_url"

vibium go https://example.com
vibium title        # "Example Domain"
vibium text h1      # "Example Domain"

vibium stop
kernel browsers delete "$session_id"

Using Vibium MCP server with Kernel

The MCP server reads the same environment variable, so AI agents can use a Kernel-powered browser:

VIBIUM_CONNECT_URL=<your-kernel-webdriver-ws-url> vibium mcp

Or in your Claude Desktop / Claude Code config:

{
  "mcpServers": {
    "vibium": {
      "command": "vibium",
      "args": ["mcp"],
      "env": {
        "VIBIUM_CONNECT_URL": "<your-kernel-webdriver-ws-url>"
      }
    }
  }
}

Benefits of using Kernel with Vibium

• No local browser management: Run automations without installing or maintaining browsers locally
• Scalability: Launch multiple browser sessions in parallel
• Stealth mode: Built-in anti-detection features for web scraping
• Session state: Maintain browser state across runs via Profiles
• Live view: Debug your automations with real-time browser viewing

Next steps

• Check out live view for debugging your automations
• Learn about stealth mode for avoiding detection
• Learn how to properly terminate browser sessions
• Learn how to deploy your Vibium app to Kernel