Source: github.com/browser-use/browser-use/releases/tag/1.0.3rc1
Browser-use has published 1.0.3rc1, a release candidate for version 1.0.3. It is not picked up by default, since plain installs still get 1.0.2, so users need to pin it with pip install 'browser-use==1.0.3rc1'.
The CLI changes cover several cases. The --cli-mcp mode now exits cleanly when the client closes the pipe before a reply. The CLI starts its own Chromium when no browser has remote debugging enabled or no display is available, and a BU_CDP_URL with nothing listening fails after 3 seconds with one clear message. Chrome running in another PID namespace, such as in containers or Cursor on Linux, is accepted through its DevToolsActivePort.
Cloud runs also change. A cancelled run now copies downloads within 10 seconds instead of holding the browser for up to 300 seconds per pass. ActionResult now drops and warns about every ignored 0.x field, not only the first one, according to the release notes, which reference pull requests #6379 and #6383.
Why it matters if you build agents
Teams that pin browser-use should pin the exact rc version to test these changes, because unpinned installs stay on 1.0.2. Anyone running the CLI in containers or without a display gets a fallback browser and faster failures on a bad CDP URL. Cancelled cloud runs free the browser much sooner, which helps long-running agent jobs.
Get stories like this every weekday
One short email with the day's agent tooling news.