Skip to main content
The Browser Use CLI (browser-use) is the command-line interface for the Browser Use platform. It does two things:
  1. 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.
  2. 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.
The core browser workflow is: navigate to a page, run 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

macOS / Linux:
Windows (run in PowerShell):

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

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.
API key stored in ~/.browser-use/config.json with 0600 permissions.

Tunnels

Expose local dev servers to cloud browsers via Cloudflare tunnels.

Profile Management

The profile 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:
  1. First command starts a background daemon for that session (browser stays open)
  2. Subsequent commands communicate via Unix socket (or TCP on Windows)
  3. Browser persists across commands for fast interaction
  4. Each --session gets its own daemon, socket, and PID file in ~/.browser-use/
  5. Daemon auto-starts when needed, auto-exits when browser dies, or stops with browser-use close
This gives you ~50ms command latency instead of waiting for browser startup each time.

File Layout

All CLI-managed files live under ~/.browser-use/ (override with BROWSER_USE_HOME):

Windows Troubleshooting

Install x64 Python (runs via emulation):
Set the version explicitly:
Restart your terminal. If still not working:
Kill zombie processes:
Delete and reinstall: