Browser Use
CLI, skill and Python library for browser control: the agent clicks, fills forms and reads pages over CDP
Install
Install or upgrade browser-use to the latest stable version with uv using Python 3.12, run `browser-use skill install` to register the skill, and connect it to my browser. If setup or connection fails, follow https://github.com/browser-use/browser-harness/blob/main/install.md.Prompt from the README to paste into the agent.
This is third-party code. Review the repository files before installing.
What it does
Browser Use gives an agent direct browser control over the Chrome DevTools Protocol. The browser-use CLI registers a skill with browser-use skill install, after which Claude Code, Codex or OpenClaw drive the browser through short Python snippets with preloaded helpers. The skill itself tells the agent to skip the browser when a plain HTTP request is enough. Besides the CLI there is a Python library for building your own browser agent with any model, and a hosted cloud option with remote browsers.
Who it is for. For developers and QA engineers who need an agent to work with websites like a person: log in, click and collect data.
Good fit when
- The task needs actions on a site: forms, navigation, logging in
- The page is rendered with JavaScript and a plain request returns an empty shell
- You want to embed a browser agent in your own Python app
Not a fit when
- The data is available via an API or a static page
- You would be bypassing site protections against their terms
Example request
Open my account on the site, find the latest invoice and note its amount and dateLimitations
Requires Python 3.11+ and uv. The BU2 model and cloud browsers need BROWSER_USE_API_KEY and the paid cloud, though the library works with other models. Access to the cloud and foreign model APIs from Russia is not guaranteed.
How to disable. Remove the browser-use skill from the agent's skills directory and the package with uv tool uninstall browser-use, or uv remove browser-use in a project.
Security check
- The agent acts in the browser on the user's behalf, including logged-in sessions
- Runs arbitrary Python code with browser helpers
README in short
The README offers three paths: a fully hosted agent via API, a CLI for existing agents, and a Python library. For the CLI there is a ready prompt you paste into your agent so it installs the package and registers the skill. The library section covers uv add browser-use, an example agent, custom tools and model choice. MIT licensed.
FAQ
Do I need a paid key?
Not for the CLI or the library with a local browser. The key is for the BU2 model and cloud browsers.
How does the CLI differ from the library?
The CLI gives a browser to an existing agent such as Claude Code. The library runs Browser Use's own agent inside your code.
Related
A skill that gathers the last 30 days of discussion on a topic from Reddit, X, YouTube, HN, Polymarket and GitHub into one brief
The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces
A fast Rust CLI for agent browser automation: accessibility snapshots with element refs, an MCP server and skills
Microsoft's official MCP server for driving a browser with Playwright through the accessibility tree, no screenshots needed