Gemini in Chrome gains cross-tab context and rollout to India, New Zealand and Canada

An assistant built into the browser

Google is expanding Gemini's role inside Chrome, turning the browser itself into the working surface for AI assistance rather than a place to visit a separate chatbot. According to a dev.to report summarizing Google's announcements, Gemini in Chrome can discuss the page a user is currently viewing, pull out key points from videos, and combine context from multiple open tabs.

The report also lists integrations with Gmail, Google Calendar, Google Maps and YouTube, allowing the assistant to draw on connected Google services while answering questions or performing tasks.

Cross-tab context

The cross-tab capability is the most notable change. Rather than working one page at a time, Gemini is described as able to compare information spread across several open tabs, such as competing product pages, multiple articles, or travel and location research spanning different sites.

For people whose work involves assembling details from many sources, the practical appeal is fewer manual handoffs: information that would otherwise be copied between windows can be gathered and condensed within a single browser session.

Rollout to new countries

Per the dev.to report, Google's March 11, 2026 announcement confirmed the expansion of Gemini in Chrome to India, New Zealand and Canada, with desktop and iOS as the initial availability focus. The report stresses that availability continues to vary by region and platform, so a capability described by Google may not be visible to every user immediately.

Android update adds agentic features

A second, Android-focused update dated May 12, 2026 is described as adding Auto Browse alongside agentic capabilities, summarization, task automation and image transformation via a feature the report names as Nano Banana.

Auto Browse signals a shift from assistance that only answers questions toward assistance that can carry out multi-step browser work. This matters on mobile in particular, since many everyday tasks, such as checking a location or comparing pages, begin on a phone rather than a desktop.

The report notes that Google has not published a complete list of supported tasks or rollout conditions for these agentic features, so their real-world behavior will need to be evaluated as access widens.

Cross-device continuity, with caveats

Google's wider Gemini ecosystem emphasizes continuing conversations across devices when users are signed in, and Chrome's updates now span desktop, iOS and Android. However, the confirmed material is far more specific about cross-tab context and cross-app integrations than about any Chrome-specific mechanism for resuming a browser task on another device.

According to the report, cross-device continuity should therefore be read as part of Google's broader signed-in ecosystem direction, not as a fully documented Chrome feature, and users should verify how it behaves on their own devices, accounts and Chrome versions.

Limits to keep in mind

As the dev.to report itself cautions, AI-generated summaries and comparisons can speed up research and first drafts, but they do not remove the need to check source material. Outputs should be reviewed before being used for customer communication, financial decisions or any other work where accuracy and context matter.

Why it matters

Moving the assistant directly into the browser changes where AI help happens: instead of copying text into a standalone chat window, users get assistance anchored to the page, video or set of tabs they are already working with. That reduces context switching, which is a real cost in research-heavy work.

The expansion to more countries also widens the population that gets this behaviour by default, while the Android update points at the bigger strategic direction: browsers evolving from tools that display information into agents that help complete multi-step tasks. The open question, which the announcements do not fully answer, is how reliable and how broadly available the agentic side will be. Teams evaluating it should focus on the places where they repeatedly move information between tabs and apps, and test whether the contextual assistance saves time without adding avoidable review work.