Gemini Spark takes over desktop Chrome
Google's agent can now drive the desktop version of Chrome, using accounts you are already signed in to and passwords saved in the browser. It books property viewings, prepares flight searches, and fills in forms, handing the task back to the user to finalize a payment, accept terms, or create an account. This is the same pattern that has settled in with Claude and the rest: the agent does everything up to the step that cannot be undone, and a person confirms that step.
Source
Gemini Spark now integrates with ChromeGoogle: The Keyword, AI · Original published August 19, 2026
Google's Gemini Spark agent can now drive the desktop version of Chrome, using accounts you are already signed in to and passwords saved in the browser.
What it looks like in practice
It books property viewings, prepares flight searches, and fills forms, then hands the task back for you to finalize a payment, accept terms, or create an account. Claude and the rest have settled on the same shape: the agent does everything up to the step that cannot be undone, and a person confirms that step.
What it means for the sites you build
A growing share of visits comes from agents that read a page as structure rather than as a picture. That favors semantic HTML, clear labels on fields, and predictable forms — which is exactly what helps accessibility too.
The reverse also holds. Sites that lean on visual tricks, hand-rolled dropdowns without ARIA roles, and forms without real labels become harder for agents, and that will show up in completed purchases.
What is not confirmed yet
Google does not publish the list of countries where auto browse is available. It does publish the conditions: auto browse runs in desktop Chrome only, needs the device language set to English and a Google AI Pro or Ultra subscription, and works in neither Incognito mode nor a school account.
Sources
Corrections
The piece said it came from secondhand reports and was not verified against a Google source, while Google's own post on Gemini Spark in Chrome was already its first source. Google's help page for auto browse has been added alongside it, and it settles what the piece left open: desktop Chrome only, the device language set to English, and a Google AI Pro or Ultra subscription. The description of where the agent stops was corrected with it — Google names finalizing a payment, accepting terms and creating an account, not payment alone. A rolling weekly page from an aggregator was removed as a source, because its content changes under the same address.
Related
OpenClaw 2026.10.2 stops long tool output from slipping credentials past redaction
A bug in OpenClaw's secret masking let a credential through whenever it straddled the boundary between two slices of a long text. The fix ships in 2026.10.2 along with repaired updates from 2026.10.1 and a new compaction default for OpenAI and Anthropic API keys.
OpenClawverified

OpenClaw 2026.10.1 lets agents search installed skills and changes how sessions message each other
OpenClaw released version 2026.10.1 on October 10, 2026, its first stable release since 2026.9.7. Agents can now search the skills installed on a machine and read only the one a task needs, instead of carrying the whole library in the prompt. Opt-in MCP Apps run beside chat, and full backups can go to an external drive or Cloudflare R2. Three changes can break existing setups: session-to-session messaging, the old required argument, and Workboard data stored before July 2026.
OpenClawverified
Claude Code 2.1.294 fixes prompt hooks that let through the actions they were written to block
Anthropic released Claude Code 2.1.294 on October 8, 2026. It fixes prompt and agent hooks phrased as instructions, which could allow exactly the actions they were meant to stop. Version 2.1.295 followed the same day with an onFailure setting that makes a crashed or timed-out command or HTTP hook block the action. Releases 2.1.292 and 2.1.293 from earlier in the week closed several permission and sandbox gaps.
Claude Code Releases (GitHub)verified
