Craig Federighi posted Apple’s WWDC 2026 teaser last week and I had my usual reaction to these things: gorgeous, probably transformative for someone, and completely irrelevant to the 23 Chrome tabs where my actual workday happens. “AI advancements” across every platform, they said. Siri did something vaguely impressive with on-device models. Developer Twitter went feral. And none of it will ever touch the inside of a browser tab.

A walled garden inside the walled garden

Apple Intelligence does useful stuff at the OS layer. Notification summaries, pulling context out of Messages, those AI portraits that sort of look like your friends if you squint hard enough. All of it runs on data Apple’s own frameworks can reach: system apps, local files, whatever developers pipe through App Intents.

But Chrome manages its own process space, its own cookies, its own session tokens, and absolutely none of that flows into Apple Intelligence no matter how good the on-device model gets. I keep seeing people suggest Safari will fix this eventually. Technically possible, sure. Safari’s market share among people doing serious browser-based knowledge work hovers somewhere between negligible and “their IT department won’t allow it,” so that line of thinking is a dead end for most professionals who actually need this solved.

Every cloud lab slams into the same thing

Google’s Gemini, OpenAI’s operator mode, Anthropic’s Claude. They’re all building from the cloud down. Start with a powerful model, bolt on tool-use and function-calling, then discover the model cannot see what you see in your browser because your session is local state that requires authentication context no cloud system should ever possess.

Someone on r/ChatGPT burned forty minutes last week trying to get an AI agent to pull numbers from their company’s Salesforce dashboard, and the agent kept demanding login credentials the user correctly refused to hand over. The model was smart enough. The plumbing was wrong.

Browser Relay

So flip the direction. Instead of shipping your browser state to some datacenter, the AI connects to your local Chrome session and operates on pages you already have open, with your existing logins and cookies intact. No credential transfer. No headless browser spinning up on a server farm in Virginia.

What actually happens after the keynote

Apple’s WWDC demos will be gorgeous because they always are. Somebody will summon Siri to orchestrate Calendar and Mail and probably a third-party app whose developer pulled an all-nighter implementing the new API just in time for the stage demo, and the audience will clap, and then every single one of those developers will go back to their hotel rooms and open Chrome and manually copy data between tabs exactly the way they did before the keynote.

Dassi lives where the keynote demos do not. It’s a Chrome extension in your side panel that reads the page you’re on, drafts replies in your email, fills forms in your internal tools, and automates the repetitive browser work that cloud agents fundamentally cannot reach. Bring your own API key or use a ChatGPT subscription. Data stays in your browser.

Billions on smarter models, zero on where they run

I find this genuinely baffling. The amount of money flowing into making models smarter is staggering, while almost nobody invests in solving where those models execute relative to the user’s actual working context. GPT-5.2 is a marvel and it still cannot see your filled shopping cart or your half-written Jira ticket, because it runs in a datacenter thousands of miles from the browser session where that cart and that ticket actually live.

And Apple is about to pour another round of stage time into AI features that work beautifully inside Apple’s own apps while staying completely blind to the web apps where most professional work happens. Same bet everyone else keeps making.

The tasks eating your workday live in authenticated browser sessions. WWDC will be a hell of a show, though.