Google Opens Gemini in Chrome to All U.S. Android Users and Extends Auto Browse to Mobile

Google expanded Gemini in Chrome to all Android users across the United States on August 18, 2026. The update introduces the browser's built-in AI assistant to mobile handsets and extends "auto browse," Google's agentic web automation feature, to smartphones for Google AI Pro and AI Ultra subscribers. The Android rollout follows the initial launch of Gemini in Chrome for desktop environments in September 2025. On mobile devices, the assistant provides on-page article summaries, contextual answe

2 min
Google Opens Gemini in Chrome to All U.S. Android Users and Extends Auto Browse to Mobile

Google expanded Gemini in Chrome to all Android users across the United States on August 18, 2026. The update introduces the browser's built-in AI assistant to mobile handsets and extends "auto browse," Google's agentic web automation feature, to smartphones for Google AI Pro and AI Ultra subscribers.

The Android rollout follows the initial launch of Gemini in Chrome for desktop environments in September 2025. On mobile devices, the assistant provides on-page article summaries, contextual answering without tab switching, integrations with Google Workspace apps such as Calendar and Keep, and on-device image editing via Nano Banana.

Mobile Multi-Step Web Automation

The primary architectural addition in the mobile release is the expansion of auto browse. Rather than acting strictly as an informational assistant, auto browse executes multi-step task workflows across web applications, such as reserving event parking, modifying recurring online orders, and managing flight or lodging itineraries.

Google Gemini in Chrome Auto Browse Architecture and Safety Pipeline

When an end user specifies a multi-step objective, the system generates a structured execution plan for review before initiating actions. The agent navigates target websites, shares necessary contextual data from connected Google accounts, and can authenticate through Google Password Manager credentials without exposing plaintext passwords to the underlying model.

Safety Boundaries and Tier Limits

To mitigate risks associated with autonomous browsing, Google implemented a multi-layered security architecture originally previewed in late 2025:

  • User Alignment Critic: A dedicated secondary model inspects proposed browser actions prior to dispatch to evaluate intent alignment and detect indirect prompt injections embedded in web page DOMs.
  • Origin and Domain Filtering: Browsing execution is constrained strictly to web domains deemed relevant to the active task plan.
  • Explicit User Checkpoints: The agent pauses execution and prompts for manual user confirmation before submitting financial details, accessing sensitive health records, completing payments, or agreeing to legal terms of service.

The feature carries distinct usage quotas based on subscription tier. Google AI Pro subscribers receive up to 20 multi-step automated task requests daily, whereas AI Ultra subscribers are allocated up to 200 daily requests.

Availability and Constraints

Auto browse remains restricted to personal Google accounts of U.S. users aged 18 and older with system languages configured to English. The capability is excluded from Incognito browsing sessions, is currently unavailable on iOS devices (iPhone and iPad), and requires administrator approval for enterprise Workspace domains.

Sources

Written by

More to read

  • Zero-Downtime Model Updates in Production LLM Serving: In-Place Weight Transfer, CUDA IPC vs. NCCL Syncing, and Traffic Draining Architectures

    Zero-Downtime Model Updates in Production LLM Serving: In-Place Weight Transfer, CUDA IPC vs. NCCL Syncing, and Traffic Draining Architectures In high-throughput LLM serving infrastructure, updating model checkpoints presents a severe operational dilemma. Traditional microservice deployment patterns such as blue-green deployments or rolling pod restarts fail to scale economically when applied to multi-GPU LLM clusters. Tearing down a serving instance to load a newly fine-tuned checkpoint or pol

    1 min
  • The Curse of Multilinguality in Large Language Models: Capacity Dilution, Tokenizer Fertility, and Representation Interference

    The Curse of Multilinguality in Large Language Models: Capacity Dilution, Tokenizer Fertility, and Representation Interference Training a single transformer foundation model to process dozens or hundreds of languages is one of the central goals of modern natural language processing. In theory, massive multilingual pre-training unlocks positive cross-lingual transfer: low-resource languages gain syntactic, factual, and reasoning capabilities from the rich supervision available in high-resource l

    1 min
  • LLM Load Shedding and Overload Control in Production: Adaptive Admission, Preemption Economics, and Graceful Degradation

    LLM Load Shedding and Overload Control in Production: Adaptive Admission, Preemption Economics, and Graceful Degradation Standard web services rely on well-established overload protection patterns: reverse proxies monitor CPU utilization, memory thresholds, or static queue depths and reject excess HTTP requests with 429 Too Many Requests or 503 Service Unavailable status codes. When applied naively to Large Language Model (LLM) serving infrastructure, these conventional heuristics fail catastro

    1 min