Google now keeps AI Mode open beside a web page in Chrome desktop after you click a link, while preserving the active search context. My read is simple: this is not a cute UI tweak. It is Google patching a workflow break that ChatGPT, Perplexity, and browser-native assistants have been exploiting for months. The old break was obvious: you ask in search, click out to a site, read, then lose the conversational state that made the first answer useful.
The article is thin, so a few core facts are still missing. It does not disclose rollout scope, timing, regional availability, or whether this is limited to Labs, paid users, or a broader Chrome cohort. It also skips the most important implementation detail: when you ask a follow-up, how much weight does AI Mode give to the page you are currently viewing versus fresh retrieval from the open web? Those are two very different products. One is basically an on-page copilot. The other is a search agent wrapped in a split-screen browser UI.
I’ve long thought Google’s problem here was never model capability in isolation. Gemini has been good enough for this class of product for a while. The pressure point is whether search behavior still happens inside surfaces Google controls. Over the last year, OpenAI kept deepening the ChatGPT search-plus-browse loop, and Perplexity has been even more explicit about turning citation, reading, and follow-up into one continuous workflow. Google Search, by contrast, still had a jagged handoff: query on Google, reading on the publisher page, next question somewhere else. Keeping AI Mode pinned beside the page is Google trying to reclaim query two and query three, not just query one.
That is why I don’t fully buy the likely product narrative that this is mainly about “helping users explore the web.” Sure, it does that. But it also keeps users inside Google’s reasoning layer while they browse other people’s content. The tension is obvious. If follow-ups heavily summarize the current page, publishers will worry that users consume the page but never continue deeper into the site. If follow-ups blend the current page with broader retrieval, then the source page loses authority inside its own reading session. Google wants both: preserve the web and mediate the web. This feature pushes that contradiction closer to the foreground.
There is also a broader browser story here that the piece does not unpack. If Chrome starts holding retrieval context across tabs or side-by-side sessions, the browser becomes the natural container for agentic work again, not just tab management. Microsoft tried parts of this with Edge Copilot, but the hard part was never getting a sidebar on screen. The hard part was making the assistant stateful with page context in a way people actually reuse. Google seems closer to the useful version now.
I still want basic evidence before praising it too much. I couldn’t find latency numbers, citation behavior, or how ads are treated when AI Mode stays live next to publisher pages. Without those details, this remains a strategically smart move with unresolved tradeoffs, not a proven win.