Browser automation tool
Persistent Browser CLI
PBC gives agents and developers a stable Chrome profile they can reopen, inspect, navigate, screenshot, and control through CDP without losing login state between runs.
How it works
A reusable browser profile for agent workflows
Open Chrome
PBC starts Chrome with a dedicated user-data directory and exposes the browser over a local CDP port.
Keep state
Login sessions, cookies, profile settings, and extension state live in the persistent profile.
Control tabs
Commands can reuse tabs, inspect page text, click, type, upload files, take screenshots, and run page JavaScript.
Use Playwright
When raw Playwright is a better fit, PBC can forward Playwright CLI commands through the same toolchain.
Setup
Install through Agent Toolpacks
Agent Toolpacks is the official packaged setup path for installing and updating PBC alongside the other local automation tools. Use it when you want a guided installer, update flow, and doctor checks instead of manually cloning the repo.
Manual command shape
pbc doctor checks Chrome, the profile path, CDP, backups, and command shims.
Common run
pbc open https://example.com opens or reuses Chrome and waits for CDP to be ready.
Clean shutdown
pbc sac saves active browser state and closes the CDP-controlled browser cleanly.
Details
Where to go next
Agent Toolpacks
Use the official Agent Toolpacks site for setup, installer access, and packaged-tool details.
Source repository
Read the implementation README, release notes, and command behavior in the public source repo.