A commit merged into the Chromium open-source repository on August 19 adds two new entries to chrome://flags for something called “Browser Actuator” — a previously unseen service Google describes internally as enabling “remote browser automation.”
The two flags are #browser-actuator (“Enables the Browser Actuator service for remote browser automation”) and #enable-browser-actuator-for-glic-experimental-triggering (“Enables using the Browser Actuator transport for Glic experimental triggering messages”).
Digging into the surrounding source code shows Browser Actuator lives in its own directory, chrome/browser/browser_actuator, separate from the existing “Actor” system that already powers Glic’s on-device agentic features — the auto-browse style tools Google rolled out earlier this year that let Gemini’s Chrome sidebar click through pages and fill forms on a user’s behalf. Browser Actuator instead defines a “TransportSession” that outside callers can connect to, plus a companion Glic component built specifically to handle messages over that transport, including requests to trigger, continue, or stop an automated “actuation” session, capture a screenshot, or record a device opt-in decision.
In other words, this looks like infrastructure for starting or steering a Glic automation session remotely, rather than only from a click inside the browser itself — though Google hasn’t described the intended use case publicly, and the code alone doesn’t say whether “remote” means a Google server, a companion device, or an internal testing harness.
Nothing here is user-facing yet. Both flags are hidden behind chrome://flags, require manual enabling, and carry no announced release date or feature description beyond the one-line summaries in the code itself.
As with any flag spotted in Chromium’s source code, this is an early, experimental signal rather than a confirmed feature. Google frequently tests changes this way and ships them later, modifies them substantially, or abandons them entirely before they ever reach a stable Chrome release.
Chrome Story will keep an eye on chrome://flags and future Chromium commits for signs of where Browser Actuator is headed, particularly whether it surfaces alongside Glic’s existing auto-browse capabilities in an upcoming Chrome release.
Questions? Theories? Let me know in the comments below.
