Skip to content
Home

/

Glossary

/

Core

/

Browser Use

Core

6 min read

Also: browser-use, browser_use, Browser Use Cloud, browser use python, browser use agent, browser-use library

Browser Use

Quick answer

Browser Use is an MIT-licensed Python library from the YC-backed startup Browser Use that lets a large language model control a Chromium browser. Install it with pip install browser-use (Python 3.11+), put an OpenAI, Anthropic, Google or Browser Use Cloud key in .env, and give an Agent a task; for options that need no code, see Browser Use alternatives.

Browser Use is an MIT-licensed open-source Python library, made by the YC-backed startup Browser Use, that lets a large language model control a Chromium browser through a loop of observing the page and choosing clicks, typing and navigation.

Last verified

What people do with Browser Use

Key facts

Made byBrowser Use (Y Combinator W25)
LicenseMIT (open-source library)
LanguagePython
Browser controlChrome DevTools Protocol (Playwright in early versions)
ModelsBring your own: OpenAI, Anthropic, Google and others
Pricing modelLibrary free; Browser Use Cloud is a paid, usage-based hosted service

What is Browser Use?

Browser Use is an open-source Python library that lets a large language model operate a web browser. You give it a task in plain language ("find the cheapest direct flight from Berlin to Lisbon next Friday"), connect an LLM, and the library runs a loop in which the model looks at the current page, chooses an action such as clicking, typing or scrolling, and repeats until it decides the task is done. It is one of the most-starred AI agent projects on GitHub, and the name is often used loosely for the whole category of "LLM drives a browser" tools.

The project is maintained by Browser Use, a startup that went through Y Combinator's Winter 2025 batch. The library is released under the MIT license, so you can use and modify it in commercial software. The company also sells Browser Use Cloud, a hosted service with managed browsers, an API, and extras that are not in the open-source package, such as stealth browsers, proxies, CAPTCHA handling and persistent profiles.

How Browser Use works

A Browser Use run has three moving parts:

  • The browser. The library launches or connects to a Chromium-based browser. Early versions were built on top of Playwright; in 2025 the team rewrote the browser layer to talk to Chrome directly over the Chrome DevTools Protocol, which they said made element extraction and screenshots faster and improved handling of cross-origin iframes.
  • The page representation. Before each step the library extracts the interactive elements on the page (links, buttons, inputs), numbers them, and sends that list to the model, optionally with a screenshot. The model refers to elements by index rather than writing a CSS selector.
  • The agent loop. The model returns one or more actions (click element 12, type into element 7, go to URL, extract content, done). The library executes them, captures the new state and asks again. You can add custom actions in Python, so the agent can call your own functions, write to a file or hit an API.
  • You bring your own model. Browser Use works with OpenAI, Anthropic, Google and other providers, and the choice of model has a large effect on both reliability and cost per task.

    Getting started

    Browser Use needs Python 3.11 or newer. Install it with pip install browser-use (or uv add browser-use), let it install a Chromium build, and put an API key in a .env file: either a model provider key such as OPENAI_API_KEY, ANTHROPIC_API_KEY or GOOGLE_API_KEY, or a Browser Use Cloud key if you use their hosted models and browsers. A script then creates an Agent with a task in plain English and an LLM, and runs it. Check the project's quickstart for the current commands, because the API has changed between releases.

    What people use it for

  • Research and data collection across sites that have no API, where writing a scraper per site is not worth it.
  • Form filling and back-office tasks, such as entering the same record into several portals.
  • Prototyping agents that need web access as one of their tools.
  • Testing, by describing a user journey and checking whether an agent can complete it.
  • Common problems

  • Cost and speed. Every step is an LLM call with a page representation attached. Long tasks can take minutes and use many tokens. Smaller models are cheaper but make more mistakes.
  • Non-determinism. The same prompt can take a different path on two runs. For a job that must run identically every day, many teams use the agent to discover the steps and then freeze them into a script or workflow.
  • Bot detection. A locally launched Chromium is easy for systems like Cloudflare Turnstile or DataDome to flag. The open-source library does not include stealth or CAPTCHA solving; the cloud product sells those separately.
  • Infrastructure. Running many agents means running many browsers, which means memory, crash recovery, session storage and logging. That is the work the hosted products charge for.
  • Logins and secrets. Passing passwords to an LLM prompt needs care; the library has a mechanism for sensitive data placeholders, but you still own the security model.
  • How it relates to automation

    Browser Use sits between classic browser automation and full no-code platforms. Compared with Playwright or Selenium, you write far less site-specific code, but you give up determinism and pay per step in model tokens. Compared with hosted agent products, you get full control and an MIT license, but you run and maintain everything yourself. Frameworks in the same space include Skyvern and Stagehand; for a broader survey see Browser Use alternatives.

    Browser Use and Autonoly

    Autonoly is not built on Browser Use. It is a hosted product rather than a library: its AI agent drives a real cloud Chromium browser through Playwright with the patchright stealth patches, and you can watch the run and take over the browser when a login or an unsupported CAPTCHA needs a human. The main practical difference is what happens after a run works: in Autonoly a finished session can be converted into a workflow that runs on a schedule without re-asking the model every step. Autonoly does not provide proxies, and its CAPTCHA solving covers reCAPTCHA v2 and hCaptcha only when enabled. If you want a Python library to embed in your own code, Browser Use is the more direct fit.

    Why It Matters

    Browser Use made LLM-driven browsing a few lines of Python, which is why so many AI agent projects start with it. Knowing what the library does and does not include (no hosting, no stealth, no scheduling in the open-source package) tells you how much infrastructure you will still be building yourself.

    How Autonoly Solves It

    Autonoly is a hosted alternative rather than a library: its agent works in a real cloud Chromium browser (Playwright with patchright), you can watch and take over mid-run, and a session that works can be converted into a workflow that runs on a schedule. It does not offer proxies, and it solves reCAPTCHA v2 and hCaptcha only when that option is enabled.

    Learn more

    Examples

    • A developer installs browser-use, connects an Anthropic or OpenAI key, and asks an agent to collect the opening hours of twenty clinics from their websites into a CSV file

    • A team uses Browser Use to discover the click path through a supplier portal, then rewrites the stable part as a Playwright script for daily runs

    • An AI assistant project registers a custom Browser Use action that saves extracted results to its own database

    Frequently Asked Questions

    The open-source browser-use library is free under the MIT license. You still pay for the LLM API calls it makes and for wherever you run the browser. Browser Use Cloud, the company's hosted service with managed browsers and extras such as stealth and proxies, is a paid, usage-based product.

    Neither, in current versions. Early releases were built on Playwright, but in 2025 the project moved to controlling Chrome directly over the Chrome DevTools Protocol. It has never been based on Selenium.

    It supports several providers, including OpenAI, Anthropic and Google models. Larger frontier models complete multi-step tasks more reliably; smaller models are cheaper and faster but fail more often on long or ambiguous tasks. Test with your own tasks, because results vary by site.

    The open-source library has no built-in stealth or CAPTCHA solving, so a plain local Chromium is often challenged by anti-bot systems. Browser Use Cloud advertises stealth browsers, proxies and CAPTCHA handling as paid features. Always check a site's terms before automating it.

    Both are open-source AI browser agents with a paid cloud. Browser Use is a Python library under the MIT license that you embed in your own code. Skyvern is AGPL-3.0 licensed and leans toward workflows, with a visual workflow builder and code generation from runs.

    The library itself has no scheduler; you run it from your own code, so you would add cron, a task queue or a hosted runner. Because each run calls an LLM at every step, many teams use the agent to find the steps and then freeze them into a deterministic script for scheduled jobs.

    Related terms, automations and guides

    Where this concept shows up in practice.

    DefinitionAI AgentAn AI agent is an autonomous software system that uses large language models to perceive its environment, make decisions, and take actions to accomplish goals with minimal human direction.DefinitionPlaywrightPlaywright is Microsoft's open-source browser automation framework that provides a single API to control Chromium, Firefox, and WebKit browsers. It supports headless and headed modes, auto-waiting, and network interception, making it a leading choice for testing and web scraping.DefinitionSkyvernSkyvern is an open-source (AGPL-3.0) AI browser automation tool from a Y Combinator S23 company that uses LLMs and computer vision to complete web tasks and workflows without hand-written selectors, available self-hosted or as Skyvern Cloud.DefinitionChrome DevTools Protocol (CDP)The Chrome DevTools Protocol (CDP) is the JSON-over-WebSocket interface Chrome exposes for inspecting and controlling the browser. Chrome DevTools, Puppeteer, Playwright and many hosted browser services use it to navigate, click, intercept network traffic and capture pages.DefinitionAI Web ScraperAn AI web scraper is an AI-powered data extraction tool that understands page structure, identifies relevant data, and extracts information from websites without requiring manual CSS selector configuration or custom scripting for each target site.DefinitionCloudflare TurnstileCloudflare Turnstile is Cloudflare's free CAPTCHA replacement: a widget that runs invisible browser checks, issues a single-use token, and lets the site verify that token server-side through the Siteverify API.DefinitionCSS SelectorA CSS selector is a pattern used to identify and target specific HTML elements on a web page, widely used in browser automation to locate buttons, forms, text, and other interactive elements.GuideAutonoly vs Skyvern: AI Browser Automation for Non-DevelopersA balanced, in-depth comparison of Autonoly and Skyvern for AI-powered browser automation. We cover architecture, features, pricing, and use cases — with honest assessments of where each tool wins.

    Stop reading about automation.

    Start automating.

    Describe what you need in plain English. Autonoly's AI agent builds and runs the automation for you — no code required.

    See Features