Gumloop Runs Browser Use Stealth Browser On-Prem for Agents

On October 6, 2026 Gumloop launched Browser for every agent, running Browser Use's stealth Chromium on-prem inside its own sandboxes — same stealth, CAPTCHAs and proxies, no data leaving.

Wire notes

  • On October 6, 2026 Gumloop launched Browser for every agent, powered by Browser Use's on-prem stealth Chromium.
  • Licenses last seven days and activate via API key exchange, so copied licenses expire quickly.
  • The timeline ran from spec on September 3 to launch on October 6, with Chrome 154 shipping on-prem October 8.
  • Opendoor uses the agents for utility turn-ons across hundreds of homes every week.
  • The browser needs egress to only four Browser Use hosts, and TLS is never broken on its residential proxies.
How Gumloop Runs Browser Use's Stealth Browser On-Prem
PhotoHow Gumloop Runs Browser Use's Stealth Browser On-Prem — 377053 / pixabay

On October 6, 2026, Gumloop launched Browser, a real Chromium browser available to every agent on its platform, powered by the Browser Use stealth browser running on-prem inside Gumloop's own cloud sandboxes rather than in Browser Use Cloud. Gumloop gets the same stealth, CAPTCHA solving and residential proxies that Browser Use runs in its cloud, while sign-ins, downloads and recordings stay in Gumloop's infrastructure.

Gumloop is a platform for building AI agents for work. When an agent meets a website with no API, no MCP server (a protocol that lets agents call external tools) and no Gumloop connector, it now opens a browser and does the work itself. The company's own docs advise preferring connectors where they exist, because connectors are faster and more reliable. But most of the web will never get one: utility portals, state filing systems, supplier dashboards, competitor checkout flows and internal tools built in 2014. Gumloop calls this "the last mile of automation". Each site is a small slice of usage, but together they make up most of what people ask an agent to do.

What does the browser actually do?

When an agent lacks a connector, it opens Chromium, navigates, clicks, types, fills forms and downloads files. When a step requires a person — a 2FA code, an SSO approval, a purchase confirmation — it hands the browser to the user and waits, according to Gumloop's docs.

The launch post lists the use cases:

  • Opendoor builds agents that handle utility turn-ons across hundreds of homes every week, pulling credentials from 1Password and coordinating across browser, email and phone.
  • Competitive research: walk a competitor's free trial, screenshot every onboarding step, check pricing and checkout pages weekly and flag changes.
  • Portals with no API: track filing deadlines, permit renewals and trademark status in state, city and federal portals; pull statements and invoices into Drive.
  • Office errands: restock snacks on Costco or Instacart, order lunch on DoorDash, book tables on Resy or OpenTable.

Gumloop also shipped a credential vault, 1Password integration, a verified identity per agent, session replays, Skills (a finished task saved as a reusable procedure), and model routing that lets a stronger model plan while a cheaper one drives the browser. On October 13 it added a mobile view and per-country proxies.

Why keep the browser inside the sandbox?

Gumloop's docs state it plainly: "The browser runs inside the same Code Sandbox as the agent." The usual alternative is a hosted browser API, which runs the browser in the vendor's cloud. For Gumloop that would have meant paying for compute twice, session data leaving its infrastructure, an extra network hop on every action, and a harder enterprise security review.

Gumloop's CTO, Rahul Behal, sent Browser Use the spec on day one. Residential proxies with country selection were a must. Persistent profiles had to live on the sandbox filesystem, and human takeover and session recordings had to work.

What is an on-prem browser?

An on-prem browser is browser infrastructure that runs in the customer's environment instead of the vendor's cloud. For Browser Use, it is the same patched Chromium build that powers Browser Use Cloud, released on the same schedule and shipped as a single binary. The agent connects via local CDP (Chrome DevTools Protocol) on 127.0.0.1:9222 instead of remote CDP over the internet. Profiles, downloads and recordings stay on the customer's filesystem, and compute runs on hardware the customer already pays for.

Stealth is a property of the build, not a plugin. A fingerprint — canvas, WebGL, fonts, screen, timezone, language — is assigned per profile and stays sticky, so a returning agent looks like the same returning user. The timezone matches the proxy's exit IP. The Chromium sandbox stays on, and leak-prone settings like device-metric overrides are locked by default. When a Gumloop customer needed agents to QA mobile layouts of its own storefronts, Browser Use added a manager switch that allows resizing, enabling the Pixel 7 mobile view shipped October 13.

How are CAPTCHAs and proxies handled?

Most CAPTCHAs are solved inside the binary, so nothing leaves the sandbox. Harder challenges go to a Browser Use solver service that receives only anonymous data — a screenshot or challenge token — and stores nothing except metadata and success rates. Customers who cannot allow that egress can self-host the solver. Whatever remains, Gumloop hands to the user.

The on-prem browser routes through Browser Use residential proxies in any supported country. The proxy runs with zero data retention, and TLS is never broken; Browser Use sees only the destination domain, which it uses to block scam and phishing domains. Customers can bring their own proxies.

How does licensing survive a user-controlled sandbox?

Gumloop raised the hardest design problem before launch: in an agent sandbox, the end user controls the machine and could copy anything the browser needs to verify. The answer has three parts. Activation exchanges a Browser Use API key for a short-lived license, renewed by a cron job. Licenses last seven days, so copied licenses expire. And the proxy needs only a server and user name — no secrets in the browser's path.

Every release ships with checksums, a signature, build provenance and an SBOM, verified by the installer. Telemetry, password saving and sync are off by default. The browser needs egress to only four hosts, which fits on a short firewall allowlist.

How fast did it ship?

The timeline moved quickly. Gumloop shared its sandbox spec on September 3. The browser binary ran outside Browser Use's cloud for the first time on September 9, and the first on-prem build arrived September 15 — Behal's verdict the same day: "The core integration is working well." A September 24 release added API-key activation, signed releases and telemetry off by default after Gumloop's launch-readiness review. On September 25, Gumloop's Max reported: "Works so impressively well. bravo guys." Chrome 154, which improved stealth on Akamai-protected sites, shipped on-prem October 8, the same week as production.

Gumloop did not adopt a new agent framework. It added one tool with raw CDP access, ported helpers from the open-source browser-use-pi agent, and built its product layer on top: live takeover, step-by-step replays, credentials typed by Gumloop so the model never sees them, and handoffs from Slack and SMS.

Browser Use advises on-prem when agents already run in the customer's sandboxes, VMs or VPC, when browser state must stay local, or when egress is restricted. As agents move into long-tail web work where bot detection lives, on-prem stealth browsing gives platform vendors a way to keep data and compute inside their own walls while still getting past the door.

via browser-use.com (Source)

Filed under

Share this article:

More from Elena Vasquez

Elena Vasquez

Show full bio

Senior reporter covering technology and product news in marketing, advertising, marketing technology, media, SEO and search at Marketing Herald.

352 articles

More on the wire

« Previous articleNext article »