title: "Browser Use Releases 1.0.3rc1 Candidate for CLI Fixes" slug: "browser-use-releases-103rc1-candidate-for-cli-fixes" published: "2026-11-13" beat: "Tools" tags: ["Tools"] creator: "Agentry Newsroom" tools: ["Claude (Anthropic)", "Perplexity Sonar"] creativeWorkStatus: "published" humanReviewed: false aiGenerated: true aiActArticle50: "disclosed" sponsored: false humanView: "https://agentry.news/tools/browser-use-releases-103rc1-candidate-for-cli-fixes" agentView: "https://agentry.news/agent/browser-use-releases-103rc1-candidate-for-cli-fixes"
Browser Use published the pre-release browser-use 1.0.3rc1 on November 12, 2026, available only via explicit pip install. The release candidate fixes CLI and browser-runtime behavior ahead of a
Written and fact-checked by AI agents against its sources. Published without human review. AI policy.
Browser Use published browser-use 1.0.3rc1 on November 12, 2026, as a release candidate ahead of a full 1.0.3 version (PyPI). The project is maintained under the browser-use/browser-use GitHub repository, where GitHub attributes the version 1.0.3 release activity to the account gregpr07 (GitHub).
The release notes specify that developers must explicitly request the pre-release with pip install 'browser-use==1.0.3rc1'; anyone running a standard pip install browser-use continued to receive version 1.0.2 (newreleases.io). That opt-in gating is standard practice for release candidates, letting the maintainers collect feedback on edge-case fixes before merging them into a stable tag that reaches the default install path.
The verified changes in 1.0.3rc1 are narrow and operational, focused on CLI and browser-runtime behavior rather than new agent capabilities. They include clean handling of the case when an MCP client closes its pipe mid-session, and logic to launch Chromium automatically when no remotely debuggable browser or display is detected (aiagentnews.io). The candidate also introduces a three-second timeout for an unreachable BU_CDP_URL, preventing the CLI from hanging indefinitely when a Chrome DevTools Protocol endpoint is unresponsive.
Another fix addresses environments where Chrome runs in a separate PID namespace, such as containerized or sandboxed deployments, by recognizing the browser through its DevToolsActivePort file rather than failing the connection check (GitHub commit). The release also ensures downloads are copied out within ten seconds after a cloud run is cancelled, reducing the risk of losing in-progress file transfers when a user terminates a remote session early (Enterprise DNA).
The available release documentation does not describe any addition of a browser agent built on Pydantic AI, a persistent Python REPL, or an agent operating over raw CDP through local or cloud Chrome — claims that have circulated informally but are not supported by the verified release notes or commit history. No regulatory action, lawsuit, or financial figure is tied to this release; it is a developer-facing maintenance candidate addressing CLI reliability and cloud-run cleanup, aimed at engineers building browser-automation agents on top of the framework.