Browser Use ships 1.0.1 with Chrome-free MCP for servers
The headline change lets `browser-use --cli-mcp` run on servers, containers and CI machines without a preinstalled Chrome: it installs and drives its own Chromium on first use, and returns one clear error when no browser can launch. Other fixes keep CLI and MCP `http_get` requests coming from the local machine, stop `allowed_domains` from being bypassed through a cloud browser, make piped CLI code and long MCP output UTF-8 on Windows, name the environment variable to set when HOME is read-only, and give each run a separate browser-harness workspace. The release installs with `uv add 'browser-use==1.0.1'`.
Why it matters
Developers running browser agents on headless servers or CI no longer have to provision a browser themselves, and domain allowlists in MCP mode now hold even when a cloud browser is in the loop.
Sources
- PrimaryBrowser Use
Written by AIToolMaps from the source above and checked against it sentence by sentence.