Pentagon signed deals last week with Nvidia, Microsoft, and AWS to deploy AI inside classified networks. The thing nobody is saying out loud: the deal exists because that’s where the work is. The data lives there. The credentials live there. So does the context. So AI is most useful sitting next to the secrets it’s allowed to read.

The same logic applies to your browser. Your logins are the classified network. And most AI browser agents can’t get inside.

The fresh-profile problem

Open any cloud AI browser agent demo. The agent loads up, opens Chrome, and lands on a login page. But it can’t see your inbox. It’s a stranger to every site you actually use.

Why this keeps happening

Most AI browser agents spawn a Chromium instance on a server somewhere. That instance comes up empty. No cookies, no session tokens, no extensions, no browsing history. It’s a brand-new profile, the way Chrome looks the first time you install it on a new laptop. So when the agent starts driving that browser, every site treats it like a stranger off the street.

Some agents try to paper over this with managed browsers — they host a Chrome profile in their cloud, you log in once, and they promise to reuse it across sessions whenever you come back to a site that needs auth. Others use remote CDP (the Chrome DevTools Protocol) to puppeteer a Chrome instance running on your machine, but in a separate window from the one you actually use. And a few attempt profile import, where they copy cookies and storage from your real Chrome into their controlled instance.

But all three are the same problem wearing different costumes. The agent is not in your tab. So your real session never quite reaches it. And whichever workaround the vendor picks, you eventually pay for it in re-logins, in 2FA codes typed twice, or in handing over credentials to a third-party Chrome profile that you cannot audit and that disappears the moment the company changes its terms.

So there’s a reason this stays a workaround instead of becoming a solution. Browser sessions are not designed to teleport. Cookies are scoped to specific browser contexts on purpose. And every workaround that tries to bridge that gap is fighting against how the web’s auth model is supposed to work.

What it costs you

Two things, mainly.

Time. If your day involves Gmail, Calendar, Notion, Linear, GitHub, and Slack, that’s six logins before your agent does a single useful thing. So people give up around login three.

Security. Now your credentials live somewhere outside the browser you trust. Session cookies, OAuth tokens, sometimes passwords. And that’s a much bigger blast radius than most users mentally signed up for when they installed something called an “AI assistant.”

What a side-panel agent does instead

Dassi runs as a Chrome extension. It lives in the side panel of the browser you already have open, on the profile you already use, with the cookies you already have. The tab on the left is yours. The agent on the right reads the same DOM you do, with the same login state, the same session, the same extensions in the way. There is no second profile. There is no remote Chrome. And there is no token handoff.

This sounds unglamorous until you set it next to what cloud agents actually have to do. A cloud agent either makes you log in again inside its sandbox, or asks for permission to import your session, or runs in a chaperoned mode where you have to re-type things every time it touches a logged-in page. But Dassi just sees the page. Because the page is already there, in your real browser, with you already authenticated. So the architecture stops being interesting and starts being invisible, which is the whole point.

Browser-native context matters more than people give it credit for. When GPT-5.2 or Claude Opus 4 feels magical reading a Gmail draft you have open, it’s not because the model got smarter that morning, but because the model finally has the same context you do, sitting in front of the same logged-in inbox you opened five minutes ago. Your filters are applied. Your draft is half-written. So the AI is not guessing what page you’re on or pretending to be you in some other Chrome window. It’s looking over your shoulder, in your tab, with your login.

A boring point that nobody fights

When the Pentagon brings AI inside the firewall, nobody calls it a breakthrough. They just say: this is where the work is. So AI has to be where the secrets live, or it cannot help with the secrets.

Browsers are no different. Your tab is the firewall. And most cloud agents pitch their tent on the wrong side of it and then ask you to throw your credentials over the wall.

If you want the version that doesn’t, Dassi is on the Chrome Web Store. For the longer architectural breakdown of every approach and what each one costs you, the post on how AI agents connect to your browser goes deeper. And if you want the cloud-vs-local angle in particular, cloud browser agents can’t see your tabs covers that ground.

Login pages exist to keep strangers out. And an agent that has to log in fresh every time is, by definition, a stranger.