Google has been quietly reshaping what a browser tab actually is. What started with tab grouping in 2020 has evolved into something more deliberate: Chrome now summarises tab content, suggests when to close them, and - in recent Canary builds - can surface tabs based on what you’re currently working on rather than the order you opened them. The tab, once a passive container, is becoming an active participant.

This isn’t a UX story. It’s an inference story.

Every time Chrome decides which tab is “relevant” to your current context, it’s making a judgment call based on page content, session duration, and browsing patterns. Google hasn’t published the full technical detail of how this works locally versus server-side, and that opacity matters. The company’s entire business model is built on knowing what you’re interested in before you do. Building that capability directly into the browser’s core navigation layer is not a neutral design choice.

The argument from Google’s side - which the company has made in various forms around its AI browser features - is that processing happens on-device. That may well be true for some of it. But “on-device” and “private” are not synonyms, and the conflation of the two has become a reliable deflection in the industry. What matters is what the model was trained on, what signals Chrome sends home regardless, and whether any of this is meaningfully opt-out.

Meanwhile, Arc and Sidekari and a handful of other browser projects have been competing on exactly this territory - smart tab management, AI-assisted organisation - and losing. Not because their features are worse, but because distribution is a wall that good ideas don’t automatically climb. Chrome has roughly 65% of global desktop browser market share according to StatCounter data. When Google ships a tab feature, it ships to most of the internet.

What’s being normalised here is the idea that your browser should understand your session. That your tabs should be interpreted, not just stored. A year ago this read as a productivity pitch. Now, with Google’s advertising business increasingly dependent on first-party signals following the third-party cookie collapse, it reads differently.

The tab used to be a rectangle with a favicon. Now it’s an input. The question of who benefits from that input isn’t being asked loudly enough.