Chromium Merges Fix for Form-Filling Failures in Chrome’s Gemini Agent

A change merged into the Chromium open-source project fixes a bug that could cause Chrome’s Gemini-powered browsing agent, internally codenamed “Glic,” to fail when filling out web forms on a user’s behalf. The fix, change 7945199, lands behind a new feature flag called GlicActorAutofillPreClick.

According to the commit message, Chrome’s agentic form-filling tool was retrieving autofill suggestions and writing them straight into form fields without first clicking on the target field. That caused failures when the page’s parsed-form data was stale, since fields could be invisible or unfocusable by the time the agent tried to fill them in. The new code has the agent click the first target field before filling it, which focuses the field, prompts Chrome’s autofill system to reparse the page, and can also reveal fields that were hidden until clicked. The full change is visible on Chromium’s Gerrit code review page.

The fix sits inside Glic, the project name Google has used internally for Gemini in Chrome since the assistant gained the ability to act on webpages rather than just answer questions about them. Chrome’s agentic features already let Gemini complete multi-step tasks like comparing products or booking appointments, pausing for user confirmation before sensitive actions like checkout. An existing “Glic actor” toggle has been testable in chrome://flags for months; this change adds a more specific, currently undocumented flag aimed squarely at autofill reliability.

For now, the fix is merged into Chromium’s source but isn’t enabled for regular Chrome users, so nothing changes in your browser today. If Google turns the flag on in a future build, anyone using Gemini’s agentic features to fill out forms automatically should see fewer failed attempts when a page’s fields aren’t immediately clickable.

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.