Gate 1
Access and rollout
Record Android and Chrome versions, U.S. location, age, English device language, signed-in account type, live Pro or Ultra entitlement, admin policy, Safe Browsing, rollout state, and auto browse permission.
Independent delegated-browsing gate
Chrome Android Auto Browse Readiness
Describe one mobile web task, the live account and plan, allowed sites and data, action authority, confirmations, monitoring, and recovery. Generate a checklist without granting access or mistaking an agent's completion message for evidence.
Four readiness gates
Gate 2
Data and sites
Name the allowed sites, signed-in sessions, Connected Apps, personal fields, destination, Password Manager use, prohibited data, retention, and access-removal owner.
Gate 3
Actions and approval
Define the exact task, budget, recipients, quantities, no-go actions, required confirmations, human-takeover steps, scope-change approval, stop condition, and duplicate-action controls.
Gate 4
Monitoring and evidence
Choose a live monitor, manual fallback, incident owner, request-limit response, prompt-injection test, actual-site verification, pending-action review, and post-task access cleanup.
Classify the next action
Ready for supervised trial
The task is reversible and low sensitivity, access is live-verified, scope is narrow, a human watches the run, and the actual website result will be checked.
Human takeover required
The workflow reaches money, terms, account creation, sensitive data, an external communication, a changed scope, or another action that needs personal review and completion.
Keep manual
The task is irreversible, high consequence, insufficiently monitored, too broadly permissioned, or lacks a reliable way to verify and recover from a wrong or duplicate action.
Minimum acceptance evidence
Run one reversible, low-sensitivity task with an explicit site allowlist and zero authority for purchase, submission, account change, or external communication. Test a scope change, a misleading page instruction, stop and takeover, duplicate prevention, limit exhaustion, and manual recovery. Verify the real site state and remove unneeded access after the run.
Review the product boundaries
Gemini in Chrome overviewSeparate the mobile assistant from the auto browse agentic layer.Access and limitsCheck rollout, account, plan, browser, protection, and request limits.Privacy and safetyReview signed-in access, data sharing, prompt injection, and human control.
Official facts checked August 19, 2026 against Google's launch and Chrome Help. Recheck rollout, account, plan, daily limits, data, site access, permissions, confirmations, and safety behavior in the live product.
Frequently Asked Questions
It creates a review checklist from the access, account, plan, site, data, action, approval, monitoring, and recovery facts you provide. It does not inspect Chrome, access a Google Account, enable auto browse, or perform a web task.
No. Google says auto browse is gradually releasing. Verify the feature in the exact signed-in account and device before planning a workflow around it.
No. Google currently lists up to 20 daily multi-step requests for Pro and 200 for Ultra, plus concurrency limits. Set a smaller internal task budget, account for retries, and keep a manual fallback.
Do not treat one approval as authority for changed sites, data, recipients, quantities, prices, or effects. Reconfirm the exact consequential action and take over when the scope changes.
No. Google says the experimental feature can make mistakes and that safeguards do not eliminate all risks. Monitor important tasks and verify the actual account or website state afterward.