browser-use) is the command-line interface for the Browser Use platform. It does two things:
- Direct browser control — navigate pages, click elements, fill forms, upload files, take screenshots, run JavaScript. Supports three browser modes: managed headless Chromium, real Chrome with existing user profiles and logins, and cloud-hosted browsers via the Browser Use Cloud API. A persistent background daemon keeps the browser alive between commands for fast ~50ms latency.
- Cloud platform management — a generic REST passthrough to the Browser Use API (v2 and v3) for managing agent tasks, cloud browser sessions, profiles, workspaces, files, skills, and billing. Anything available in the cloud dashboard is accessible from the terminal.
state to get numbered element indices, then interact using those indices. The cloud workflow is: cloud login to authenticate, then use cloud v2/cloud v3 commands to hit any API endpoint, or cloud connect to provision and drive a cloud browser directly.
Installation
Prerequisites
One-Line Install (Recommended)
macOS / Linux:Install the Skill
The CLI is most powerful when paired with its skill, which gives your coding agent full context on every command, flag, and workflow. It is highly recommended to install the skill alongside the CLI:Post-Install
Manual Installation
If you prefer not to use the one-line installer:From Source
Quick Start
Browser Modes
All Commands
Navigation
Inspection
Interaction
Tabs
Cookies
Wait
Get (Information Retrieval)
JavaScript & Data
Python (Persistent Session)
Cloud API
Generic REST passthrough to the Browser-Use Cloud API, plus cloud browser provisioning.~/.browser-use/config.json with 0600 permissions.
Tunnels
Expose local dev servers to cloud browsers via Cloudflare tunnels.Profile Management
Theprofile subcommand delegates to the profile-use Go binary, which syncs local browser cookies to Browser-Use cloud.
The binary is managed at ~/.browser-use/bin/profile-use and auto-downloaded on first use.
Session Management
Global Options
Examples
Fill a Form
Extract Data with JavaScript
Python Automation
Generate Templates
How It Works
The CLI uses a multi-session daemon architecture:- First command starts a background daemon for that session (browser stays open)
- Subsequent commands communicate via Unix socket (or TCP on Windows)
- Browser persists across commands for fast interaction
- Each
--sessiongets its own daemon, socket, and PID file in~/.browser-use/ - Daemon auto-starts when needed, auto-exits when browser dies, or stops with
browser-use close
File Layout
All CLI-managed files live under~/.browser-use/ (override with BROWSER_USE_HOME):
Windows Troubleshooting
ARM64 Windows (Surface Pro X, Snapdragon laptops)
ARM64 Windows (Surface Pro X, Snapdragon laptops)
Install x64 Python (runs via emulation):
Multiple Python versions
Multiple Python versions
Set the version explicitly:
PATH not working after install
PATH not working after install
Restart your terminal. If still not working:
Failed to start daemon error
Failed to start daemon error
Kill zombie processes:
Stale virtual environment
Stale virtual environment
Delete and reinstall: