How Gumloop Runs Browser Use's Stealth Browser On-Prem
Browser Use now has an on-prem version of its stealth browser, and Gumloop is running it inside the same sandbox as its agents instead of using Browser Use Cloud.
It's the same patched Chromium build that powers Browser Use Cloud, released on the same schedule and shipped as a single binary. That means the same stealth fingerprints and built-in CAPTCHA solving. Residential proxies are optional, through Browser Use or your own. Sign-ins, downloads, recordings, and profiles stay on your own filesystem. Gumloop's agents use it when a site has no API, MCP server, or connector.
Setup is an install script on Debian 13 (amd64) with sudo. Then you activate it with a Browser Use API key and start it:
- curl -fsSL https://releases.browser-use.com/on-prem/install.sh | sudo sh
- browser-use activate
- browser-use run --config /etc/browser-use/config.yaml --profile default
The browser listens for the Chrome DevTools Protocol on 127.0.0.1:9222. Playwright, Puppeteer, the Browser Use agent, or your own harness can drive it from there. A YAML config sets headless or headful mode, the proxy, and named profiles. With no display attached, it falls back to headless on its own.
Each profile gets its own sticky, realistic fingerprint, so a returning agent looks like the same returning user. The timezone is set to match the proxy's exit location. The Chromium sandbox stays on, and device-metric overrides are blocked unless you opt in. Browser Use says on-prem customers got the Chrome 154 update, which it says improved stealth on its benchmark, the same week as its cloud.