Browser Use MCP now drives its own Chromium when your Chrome can't connect

Browser Use's MCP server now brings its own browser. On a server, container or CI box with no Chrome, it installs Chromium on first use. If no browser can run, you get one clear error.

Slide text

+ 01

Browser Use MCP now drives its own Chromium

On servers, containers and CI boxes with no Chrome, installed on first use

Release notes, Nov 10 · Pull request #6369

With remote debugging off in Chrome, about three hundred and ninety Macs and PCs never reached a browser. Now MCP runs its own Chromium. It tells your agent how to switch to your Chrome; until then, your logins stay behind.

Slide text

+ 02

Chrome's remote debugging off? MCP no longer dead-ends

The fallback Chromium has none of your logins until you switch

Release notes, Nov 11 · Pull request #6376

Slow pages get more time from the command line and MCP. Browser calls wait twenty seconds instead of five, like the agent. A page stuck behind a JavaScript dialog fails in two seconds and says to handle the dialog.

Slide text

+ 03

Slow pages get 20 seconds, not 5

• + The CLI and MCP now wait as long as the agent
• + A page frozen by a JavaScript dialog fails within 2 s
• + That error says to handle the dialog

Release notes, Nov 11 · Pull request #6376

If you set a timeout on a run, the final answer now arrives before it runs out. Provider retries stay inside it, and an answer on the last step is no longer lost.

Slide text

+ 04

With timeout=, the answer arrives before the deadline

Provider retries stay inside it, and an answer on the last step is no longer lost

Release notes, Nov 10 · Pull request #6369

You can now tell the Browser Use team what broke without leaving your work. There's a command, a Python function, a tool for the agent and one for MCP clients. Text is scrubbed before it leaves.

Slide text

+ 05

Tell the team what broke, from the terminal or the agent

$ browser-use feedback "..."
>>> browser_use.feedback("...")
agent:  report_issue(...)
MCP:    browser_feedback

Release notes, Nov 11 · Pull request #6376

Usage stats now carry error messages, visited pages and the final result. All scrubbed, and your task text is never sent. Turning telemetry off now stops everything.

Slide text

+ 06

Usage stats now include errors, URLs and the final result

• + All scrubbed; URLs lose their query string
• + Your task text is never sent
• + browser-use telemetry disable stops everything

Pull request #6369

Three more fixes. MCP domain limits can't be dodged through a cloud browser. Plain web fetches run from your machine. And on Windows, accented and Chinese text stops garbling.

Slide text

+ 07

• + --mcp domain limits can't be bypassed through a cloud browser
• + http_get in the CLI and MCP fetches from your machine
• + Windows: piped code, MCP output and open() are UTF-8

Release notes, Nov 10 · Release notes, Nov 11

If you run Browser Use through MCP, in Cursor or on a server, I'd upgrade today: that's where it most often never reached a browser. The release notes on GitHub list every fix.

Slide text

+ 08

Run Browser Use through MCP? I'd upgrade today

Release notes on GitHub

browser-use/browser-use

Release notes · github.com/browser-use/browser-use