# browser-use publishes 1.0.0rc2, a release candidate for its 1.0 line

published: 2026-11-09T17:05:26.246Z
topic: frameworks
source: https://github.com/browser-use/browser-use/releases/tag/1.0.0rc2
url: https://aiagentnews.io/stories/browser-use-publishes-1-0-0rc2-a-release-candidate-for-its-1-0-line

The browser-use project has released 1.0.0rc2, a pre-release candidate for version 1.0, which must be installed explicitly. The new version replaces the agent engine so the agent writes Python in a persistent REPL instead of picking one action per step.

The release is not installed by default: plain pip install browser-use and uv add browser-use still resolve to 0.13.14 until 1.0.0 ships. Developers need to pass a pre-release flag or pin browser-use>=1.0.0rc2, and Python 3.11 or newer is required.

In 1.0, Agent uses bu-fast on the Browser Use gateway by default, and Browser() opens a cloud browser rather than local Chromium. Local tasks on localhost or private IPs need Browser('chromium'). The default run() limit drops from 500 steps to 100, and a rejected key or model now returns status='error' on the result instead of raising.

Many 0.x options and imports are removed or changed, and the project says removed imports raise an ImportError that points to MIGRATING.md. Benchmark results on BU Bench v2 are included in the release notes, with the default mode scoring 62.6 and costing $0.071 per task.

## Why it matters if you build agents

Agent code that relied on 0.x defaults, such as local browsing, the 500-step limit or per-provider keys, needs review before moving to 1.0. Tasks against localhost will fail on the default cloud browser unless they use Browser('chromium').

Developers can check run results through result.error and status rather than expecting exceptions after configuration succeeds. Dependencies are pinned exactly, so projects that need different versions of pydantic or mcp may be unable to install 1.0 alongside them.