browser-use
Fast, persistent browser automation with session continuity across sequential agent commands.
- Supports three browser modes: headless Chromium, real Chrome with profile support, and cloud-hosted remote browsers with proxy configuration
- Includes 20+ command categories covering navigation, page inspection, interactions, data extraction, cookie management, JavaScript execution, and wait conditions
- Offers cloud session management, local server tunneling via Cloudflare, and parallel subagent execution through remote sessions with task monitoring
- Built-in Python integration for setting variables, accessing the browser object, and running scripts within the automation context
Browser Use
Direct browser control via CDP. For task-specific edits, use agent-workspace/agent_helpers.py. For setup, install, or connection problems, read https://github.com/browser-use/browser-harness/blob/main/install.md.
When Not to Use
A basic fetch of public information needs no browser. If a plain HTTP request can read it — a public page, an API, docs — use curl or your fetch tool, and leave the browser alone. Use browser-use when the task needs interaction (click, type, navigate), the user's logged-in session, JS rendering, or a bot-protected page. If a direct fetch fails or returns a shell page, then escalate to the browser.
Domain skills are off by default. Set BH_DOMAIN_SKILLS=1 to enable them; see the bottom section.
If BH_DOMAIN_SKILLS=1 and the task is site-specific, read every file in the matching $BH_AGENT_WORKSPACE/domain-skills/<site>/ directory before inventing an approach.
Usage
browser-use <<'PY'
print(page_info())
PY
More in Agent workflows
find-skills
Discover and install skills from skills.sh directly inside an agent session
vercel-labs/skillsagent-browser
Full browser automation: navigate, click, fill forms, extract data, and screenshot
vercel-labs/agent-browserskill-creator
Create, test, and publish new skills from within your agent
anthropics/skillsbrainstorming
Structured ideation and problem decomposition frameworks
obra/superpowerssystematic-debugging
Hypothesis-driven debugging loop: observe, hypothesize, test, verify
obra/superpowers