--- title: "Gemini in Chrome: user agent and token | Agent Ready Crawlers" description: "Gemini in Chrome from Google: no robots.txt token, task agent purpose and what a site can check; no exact user-agent string is published. Read 2026-11-04." canonical: https://agentreadycrawlers.com/crawlers/gemini-in-chrome site: "Agent Ready Crawlers" last_updated: 2026-11-04 section: "Crawlers" --- # Gemini in Chrome: user agent and token | Agent Ready Crawlers > Gemini in Chrome from Google: no robots.txt token, task agent purpose and what a site can check; no exact user-agent string is published. Read 2026-11-04. Source: https://agentreadycrawlers.com/crawlers/gemini-in-chrome Site: Agent Ready Crawlers Last reviewed: 2026-11-04 Browsing agent from Google # Gemini in Chrome (auto browse) In short Gemini in Chrome (auto browse) is Google's browsing agent. Gemini in Chrome has no robots.txt token, so robots.txt cannot address it and the crawl cannot measure a block rate. The operator publishes nothing a site can check. Verisoul reports caps of 20 tasks a day on AI Pro and 200 on Ultra. Operator [Google](https://agentreadycrawlers.com/crawlers/operator/google/) Vendor profile: [Google](https://agentreadycrawlers.com/vendors/google/) Purpose Task agent [All task agent rows](https://agentreadycrawlers.com/crawlers/purpose/task-agent/). A browsing agent that clicks, fills forms and finishes a job for a person. User-agent string No exact string is published. What the operator or a third party says: The user's own Chrome user agent; no marker in local mode robots.txt token None. No robots.txt line can address this agent. Respects robots.txt No documentation operator publishes no bot documentation (checked 2026-11-04) for auto browse in the user's own Chrome; Google's cloud agents declare Google-Agent instead. [Source](https://www.verisoul.ai/agents/chrome-auto-browse), read 2026-11-04. Operator publishes no bot documentation (checked 2026-11-04). Verification Nothing published The operator publishes no list, reverse DNS pattern or key directory a site owner can check. [Documentation](https://www.verisoul.ai/agents/chrome-auto-browse), read 2026-11-04. IP ranges Not published. Rate behaviour Verisoul reports caps of 20 tasks a day on AI Pro and 200 on Ultra. Block rate None: the agent has no token, so a robots.txt block rate does not exist. Documentation Operator publishes no bot documentation (checked 2026-11-04). [Closest page read](https://www.verisoul.ai/agents/chrome-auto-browse). Note. Auto browse launched 2026-01-28 as a US preview for AI Pro and Ultra subscribers, per Verisoul (secondary). It hands control back to the person to pay or accept terms. ## Allow and refuse lines This agent has no robots.txt token, so there are no lines to copy. Without a token, a published list or a signature, a site owner cannot tell it from an ordinary visitor by request alone. Refusing or allowing in robots.txt states a preference. For this row the operator or its documentation says robots.txt may not govern the fetch, so enforcement belongs in your WAF. ## Google in the Verification Ledger Five IP lists, reverse DNS for every class, and an experimental key directory for Google-Agent. Nothing for auto browse in the user's Chrome. [All operators](https://agentreadycrawlers.com/verification/). IP lists - [developers.google.com/static/search/apis/ipranges/googlebot.json](https://developers.google.com/static/search/apis/ipranges/googlebot.json) - [developers.google.com/static/search/apis/ipranges/special-crawlers.json](https://developers.google.com/static/search/apis/ipranges/special-crawlers.json) - [developers.google.com/static/search/apis/ipranges/user-triggered-fetchers.json](https://developers.google.com/static/search/apis/ipranges/user-triggered-fetchers.json) - [developers.google.com/static/search/apis/ipranges/user-triggered-fetchers-google.json](https://developers.google.com/static/search/apis/ipranges/user-triggered-fetchers-google.json) - [developers.google.com/static/search/apis/ipranges/user-triggered-agents.json](https://developers.google.com/static/search/apis/ipranges/user-triggered-agents.json) Reverse DNS crawl-\*.googlebot.com, geo-crawl-\*.geo.googlebot.com, rate-limited-proxy-\*.google.com, \*.gae.googleusercontent.com, google-proxy-\*.google.com Key directory https://agent.bot.goog/.well-known/http-message-signatures-directory (Google-Agent, subset of requests, experimental) Cloudflare not checked Visa TAP registry no public operator-level registration found (checked 2026-11-04) Mastercard Agent Pay no public operator-level registration found (checked 2026-11-04) ## Other Google rows - [Googlebot](https://agentreadycrawlers.com/crawlers/googlebot/) Search index token Googlebot - [Google-Extended (control token)](https://agentreadycrawlers.com/crawlers/google-extended/) Training token Google-Extended - [Google-CloudVertexBot](https://agentreadycrawlers.com/crawlers/google-cloudvertexbot/) Other token Google-CloudVertexBot - [GoogleOther](https://agentreadycrawlers.com/crawlers/googleother/) Other token GoogleOther - [Storebot-Google](https://agentreadycrawlers.com/crawlers/storebot-google/) Search index token Storebot-Google - [Google-Agent](https://agentreadycrawlers.com/crawlers/google-agent/) Task agent no token - [Google-GeminiNotebook (was Google-NotebookLM)](https://agentreadycrawlers.com/crawlers/google-gemininotebook/) Live answer fetch no token ## Sources - [verisoul.ai: chrome auto browse](https://www.verisoul.ai/agents/chrome-auto-browse) read 2026-11-04 - [Verify requests from Google](https://developers.google.com/crawling/docs/crawlers-fetchers/verify-google-requests) read 2026-11-04 Last reviewed 2026-11-04