Google pushed a line into its AI Mode changelog this week that I keep rereading: AI Mode can now “link and interact with select apps.” I read it twice. The word carrying the whole announcement is select.

Because select means Google chooses. Somebody in Mountain View decides which apps earn a server-side integration, signs the partnership, ships the connector, and adds it to a list. If your app made the list, wonderful. If it didn’t, you wait for a quarter that may never come. And the interaction never happens inside your app anyway. It happens across a pipe Google built between its own servers and a partner’s API, with your request making the round trip in the middle.

What “select” quietly costs you

The app-linking model is a gauntlet with a lot of gates, and every gate is a place where the thing can fail to exist, silently break after an API version bump, or leak something it shouldn’t. The partner has to want in. Google has to approve. Someone has to babysit the connector forever. Your data has to leave your machine, hit Google, get routed to the partner, and come home.

That’s four hops for a task you could do yourself in one tab.

And the list will always be short, because server-side connectors don’t scale to the long tail of software people actually use. Google will wire up the apps with the biggest logos and the cleanest APIs. Your regional bank’s clunky portal, the internal tool your company built in 2019, the niche CRM your team refuses to leave. None of those are getting a Google partnership. Ever.

Your browser skipped the whole line

A browser agent asks for none of that. It works inside the tab you already have open.

You’re logged into your email, your CRM, your invoicing dashboard, your project tracker. The session is live. The cookie is sitting right there in the browser doing its job. An agent that lives in the side panel sees the same rendered page your eyes see and clicks the same buttons your mouse would. There’s no partnership to negotiate, no connector to maintain, no approval queue. If you can load the page and you’re signed in, the agent can act on it.

Dassi works this way on purpose. It’s a Chrome extension that reads the tab you’re on, so the moment you’re authenticated, so is it. You can read more about why cloud agents can’t do this, but the short version is that login state doesn’t travel. It lives in your browser, and the only agent that gets to use it is one that lives there too.

The whitelist isn’t a bug. It’s the whole business.

I want to be fair to Google here, so let me name the constraint honestly: they curate because they have to. A server-side integration is a contract. It needs a willing partner on the other end, a stable API, an SLA, someone to page at 3am when Salesforce changes an endpoint. You cannot ship that for ten thousand apps. You ship it for forty, put out a press release, and call it “select.”

So the whitelist isn’t Google being stingy. It’s the only shape this architecture can take. Which is exactly why it’s the wrong architecture for most of what people do all day.

What this looks like on a Tuesday

Say you need to pull the last three months of transactions out of a payment dashboard that has no export button and definitely no Google integration. On the app-linking model, you’re stuck. The app isn’t select. Done.

With a browser agent you open the dashboard, you’re already logged in, and you tell it to read the table and hand you a CSV. It works because the data was already on your screen. Nobody had to approve anything. Nobody at Google ever saw the numbers. The task happened where the task lives.

I think that’s the real split here, and it’s not about model quality. Google’s AI Mode is smart. The model isn’t the bottleneck. The plumbing is. One approach routes your work through a curated cloud partnership. The other one just does the work in the place you were already doing it, with the credentials you already have. If you want to see the difference in practice, Dassi is on the Chrome Web Store and it’s free.

“Select apps” is a fine headline for a keynote slide. It’s a lousy answer when the app you need happens to not be on the list, which, statistically, it usually isn’t. Your browser never had a list. That was kind of the point of a browser.