epiral/bb-browser v0.8.0

v0.8.0 — No extension needed

on GitHub

Breaking: Chrome extension removed

bb-browser no longer requires a Chrome extension or daemon. It manages its own Chrome instance and connects directly via CDP.

New setup

npm install -g bb-browser
bb-browser site twitter/search "AI"  # Chrome auto-launches, just works

That's it. No extension to install, no daemon to start.

How it works

bb-browser launches a dedicated Chrome instance (--remote-debugging-port=19825) with its own profile at ~/.bb-browser/browser/. Log in to your sites once in the bb-browser Chrome window — your sessions persist across restarts.

What's new

• CDP direct connection — CLI connects to Chrome via WebSocket, no middleware
• Managed Chrome — auto-launches with profile name "bb-browser" in title bar
• SQLite history — reads browser history directly from Chrome/Edge/Brave/Arc SQLite files, no extension permission needed
• Auto port discovery — finds OpenClaw CDP, managed Chrome, or launches a new instance
• --port flag — connect to any CDP endpoint manually
• All actions implemented — eval, click, snapshot, network, console, frame, dialog, trace

Migration from v0.7.x

1. Uninstall the Chrome extension (no longer needed)
2. npm install -g bb-browser@latest
3. Run any command — Chrome will auto-launch
4. Log in to your sites in the new bb-browser Chrome window (one-time)

OpenClaw users

--openclaw still works. bb-browser auto-detects OpenClaw's CDP port.

Install

npm install -g bb-browser