Gumloop runs Browser Use's stealth browser locally in its own sandbox
Understand this story
Gumloop runs Browser Use's stealth browser directly inside its own cloud sandbox rather than Browser Use Cloud, thereby retaining stealth, CAPTCHA-solving and residential proxy capabilities, with login, download and screen-recording data staying on Gumloop's own infrastructure. According to Browser Use, the browser must be installed with sudo on Debian 13 (amd64), activated with a Browser Use API key and then run as a regular user; it requires access to the releases, enterprise and ip domains, and when using its proxy, access to proxy.browser-use.com as well. The license is valid for seven days, and telemetry is off by default unless the user actively enables it.
AI overview based on source reports · Updated 58 min ago
Coverage timeline
Follow the coverage to explore different perspectives.
- Browser Use BlogHow Gumloop Runs Browser Use's Stealth Browser On-Prem
Browser Use describes how Gumloop runs its stealth Chromium browser inside Gumloop's own cloud sandboxes rather than in Browser Use Cloud, giving agents the same stealth, CAPTCHA solving and residential proxies while keeping sign-ins, downloads and recordings in Gumloop's infrastructure. The on-prem browser is installed as a single binary on Debian 13, driven locally over CDP on 127.0.0.1:9222, and licensed through short-lived API-key activation rather than key files. The post also covers the timeline of the Gumloop integration, from the September 3 spec through Gumloop's October 6, 2026 launch of Browser for every agent and its October 13 mobile view and per-country proxies.
Activity for this story
Not enough continuous observations to show a trend yet.