AGENT PROFILES

Browser Use

Browser Use · Agent builders

Run browser agents as a Python library or hosted service. The product family also offers a CLI for existing agents and standalone browser infrastructure.

Browser Use · Browser agent library and cloud services

Product and access

The Python library runs a browser agent; the hosted Agent API runs both agent and browser. The separate Browser API provides browser infrastructure for your own agent code. The CLI extends existing agents.

Provider

Browser Use, Inc. provides an open Python agent library plus hosted agents and browser infrastructure. Cloud billing separates model costs, the agent markup, browser time and proxy traffic.

Operator
Browser Use, Inc.
Organization
Company
GitHub stars
117,341 · Reviewed
License
MIT
Provider sourcesSource 1 Source 2 Source 3 Reviewed
01

Core features

6 features from provider sources · checked on 9 October 2026. Availability and limits are listed below.

  • Run a browser agent in Python

    The library accepts a task and model and runs the agent through Python code.

    Source 2
  • Assign work to a hosted agent through an API

    The cloud API starts an agent run and returns the result and generated files.

    Source 4
  • Extend existing agents through the CLI

    The CLI gives existing agents access to local Chrome or a cloud browser.

    Source 4
  • Use browser infrastructure separately

    The Browser API provides a cloud browser that your own code controls through CDP.

    Source 3
  • Choose browser configuration

    Browser instances can be configured with options such as a visible window, viewport and proxy settings.

    Source 5
  • Copy selected logins

    Profile Sync copies selected cookies from local Chrome to a cloud profile.

    Source 4
02

Requirements and limits

  • Requirement

    Set up the local runtime and model access

    The guide installs a Python environment, the library and Chromium. The chosen model provider requires appropriate credentials.

    Source 2
  • Requirement

    Sync cloud profiles explicitly

    Profile Sync copies selected Chrome cookies into a cloud profile. The transfer is started explicitly and does not subsequently happen automatically.

    Source 4
  • Limitation

    Stop cloud browsers explicitly

    Disconnecting a CDP connection does not stop the managed browser. The cloud API requires a separate stop call.

    Source 3
  • Requirement

    Prepare the cloud connection

    The CLI requires sign-in before its first cloud connection. Profile Sync is run explicitly for selected accounts.

    Source 4

Operation & oversight

Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured.

Deployment covered: Browser Use Cloud: sessions and persistent profiles

Sources reviewed:

  • Documented with conditions

    Files and work state

    A session can run several tasks sequentially. Durable file retention remains open in the reviewed session reference.

    Evidence
  • Documented with conditions

    Authentication

    Profiles preserve cookies and local browser state across sessions. State is saved on sessions.stop(); parallel sessions start from a snapshot.

    Evidence
  • Documented

    Starting further runs

    Tasks start through the SDK and can reuse an existing session.

    Evidence
  • Open in reviewed sources

    Human intervention

    The reviewed session reference does not establish a mandatory per-action approval mechanism.

    Evidence
  • Documented

    Detecting errors

    A live URL enables monitoring of the running session.

    Evidence
  • Open in reviewed sources

    Recovering from errors

    General automatic recovery after interruptions remains open in the reviewed reference.

    Evidence

Editorial assessment

Profile maintenance and clean session shutdown are relevant operational tasks. Stored cookies alone do not establish indefinitely valid authentication.

03

Practical tasks

Editorial examples based on documented features. No product tests performed.

01

Compare public offers

Your input
Selected public URLs, comparison criteria and table format.
Possible result
A browser run with a comparison table and references.
What to check
Check prices, details and references directly on the pages.
02

Run your own browser workflow in the cloud

Your input
Your own Playwright workflow, cloud access and a bounded test dataset.
Possible result
Your own workflow on a cloud browser connected through CDP.
What to check
Check the result, session permissions and successful stop call.
EDITORIAL EXAMPLE

Compare public product pages in a browser and create a table with references.

Your possible prompt

Design a process for new requests: capture information, sort it by topic, and create a proposed response. Plan an approval step before external actions.

Getting-started idea based on documented capabilities. Not an executed product test. Adapt the task, data, and permissions.

04

Setup and pricing

Setup

Install the local library and browser or set up cloud access; configure a model and required website logins

Prices and included usage

Pricing checked

Cloud billing charges browser time and proxy traffic. Browser Use Agents adds 20 percent to model costs; the local MIT library has a separate cost structure.

Python-Bibliothek
USD 0 software license

Local agent runtime; your own browser operation and model access.

Price source
Cloud Browsers
USD 0.02/hour + traffic

Browser infrastructure only; residential proxy USD 5/GB.

Price source
Cloud Agents
Model costs + 20%; browser time and traffic extra

Hosted agent execution; individual model rates are listed on the pricing page.

Price source
  • Self-hosting adds infrastructure and, where applicable, model costs. OpenAI's price list is one example of separately billed model access: https://developers.openai.com/api/docs/pricing
  • Cloud credits do not expire; the pricing page describes pay-as-you-go billing without a subscription.

Pricing details

05

Sources and evidence

Official repository, product map, local and cloud guides, and pricing page reviewed on 9 October 2026. The Agent API and browser-only infrastructure are separate offerings. Examples are editorial; no browser runs were performed here.

Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.

Read profile as Markdown

How we assess the sources