I read the headline “Notion just turned its workspace into a hub for AI agents” on Hacker News this morning and immediately wondered who actually does their entire job inside Notion all day.

Notion’s pitch is that the workspace becomes the command center. You write a doc, summon an agent, and it works across your pages, your databases, your meeting notes. Fine. That’s a real thing for teams who have committed to Notion as their second brain.

But my second brain is a browser with 47 tabs open.

The walled garden problem

The agents Notion shipped see Notion. They can summarize pages, draft from databases, and chain actions across your workspace. The moment you need them to glance at the Linear ticket your engineer pasted into Slack, or pull the latest Salesforce note, or check what’s actually in that Gmail thread you’ve been ignoring for a week, they hit the edge of the property and stop.

Every SaaS company building “agents” right now is doing this same thing. ChatGPT has connectors. Notion has agents. Salesforce has Einstein. Each one promises an AI assistant that lives where you work, but the definition of “where you work” is suspiciously the same as “inside our product.”

So now you have five agents, each blind to the other four.

What the workflow actually looks like

A real Tuesday for me: I open Gmail to check a customer reply. I tab to Linear to update the ticket. I go to GitHub to look at the PR the email referenced. I pop into Notion to update the spec. I tab to Stripe to check whether the customer is on the right plan. Then back to Gmail to reply.

Notion’s agent watched one of those six steps. The other five happened in tabs it has never heard of.

This is what people mean when they say AI productivity gains are stuck. Not the model. The plumbing.

Why the browser keeps winning this fight

A browser agent has a structural advantage that almost nobody is talking about clearly: it sits one layer above all of these apps. Gmail, Linear, Notion, Salesforce — they’re all websites. The browser already has every session token, every cookie, every login state. Nothing needs to integrate with anything, because the user already integrated with everything when they logged in.

This is the angle I keep coming back to. Dassi runs as a Chrome extension and operates whatever tab you’re on, using the auth you already have, on the LLM key you already pay for. There’s no OAuth dance to grant a third party access to your Gmail. There’s no MCP server farm to configure. The tab is already yours, and the agent reaches into it the same way you do, by being in the browser.

I wrote about why cloud browser agents can’t see your tabs a while back, and the Notion launch is the same story flipped sideways. Cloud agents can’t see your local sessions. App-native agents can’t see anything outside the app. Both fail for the same underlying reason: they do not live in the layer where your real workflow happens.

The integration treadmill

Every time a new SaaS company announces agents, the response is to add yet another connector somewhere. ChatGPT supports dozens of MCP servers now, and Notion will probably grow a similar list. Some of those connectors will be useful. Most will be half-maintained adapters that break when the upstream API changes, and the user gets the joy of debugging why their agent suddenly can’t read attachments anymore. I covered the broader version of this in 40 MCP tools and it still can’t fill out a form.

A browser agent skips that entire treadmill. If you can load the page, the agent can read it. If you can click the button, the agent can click it. No integration, because there’s nothing to integrate. The websites already exist and the browser already renders them.

Damn, it’s so much simpler I keep being surprised more people haven’t noticed.

Notion doing a Notion thing

None of this is a knock on Notion. Building agents inside Notion makes total sense if you sell Notion. The mistake is on the user side, where people read the announcement and assume the agent will work the way they imagine: across the actual surface area of their job.

It won’t. It works inside Notion. That’s the product.

So where does that leave the rest of us

If you want an agent that sees what you see, you have to put it where you actually look. Which is the browser, every weekday, for hours. Dassi is in the Chrome Web Store if you want the version that doesn’t pretend your work lives in one place.

I’ll keep my 47 tabs.