Cloudflare shipped Kitesurf, a browser built specifically for AI agents, and the part I keep chewing on isn’t the browser itself. It’s where it wakes up.

Kitesurf runs on Cloudflare’s edge. That’s the whole pitch and it’s a decent one: a browser instance spun up close to the content, no local Chrome to babysit, no VM fleet, no Playwright process quietly leaking memory on someone’s laptop. Fast and clean. But “clean” is carrying enormous weight in that sentence, because clean here means empty. No cookies. No logins. No session state. Kitesurf is a rental car, and it has never met you.

An empty browser is fine right up until the work is behind a login

Ask an agent to pull competitor pricing off a public marketing page and an anonymous edge browser is perfect. Ask it to pull your invoices out of Stripe, reply to the four emails you flagged this morning, update the deal stage in your CRM, or export the report your analytics vendor charges $100/month extra to export, and the anonymous browser stops at a login wall. Then it does the worst thing a computer can do, which is ask you for a password.

I’ve watched people try to route around this. You hand the cloud browser a stored credential set, or you set up OAuth for each service, or you build a session-injection layer that copies cookies from your real browser into the remote one and then breaks every time a token rotates or the site fingerprints the IP and decides the login came from Ashburn, Virginia. That last approach is where a lot of teams end up, and it is a hell of a lot of plumbing to arrive at a browser you already had open.

Because the browser where you’re logged into everything is sitting on your desk right now.

The 10% stories are about this

Kitesurf landed in the same week as another round of “AI gains are 10%, not 10x” coverage. Measured deployments, real orgs, modest numbers. Setup and auth friction keep showing up in the postmortems, and I don’t think that’s incidental.

The model isn’t the bottleneck. GPT-5.2 and Opus 5 can both read a Salesforce opportunity page and know exactly which field to change. What they can’t do is get past the SSO prompt from a datacenter in another state. So the pilot narrows to public web research and summarization, the two things that work without credentials, and then someone measures the productivity lift and finds 10%. We wrote about that gap in setup friction and I think Kitesurf is about to generate a fresh batch of examples.

Where it does make sense

Cloudflare sits in front of a giant slice of the web, so building the agent-side browser is a smart position. Scraping, crawling, price monitoring, availability checks, anything at scale across sites that don’t know or care who’s asking. Server-side jobs where a human isn’t in the loop. It’s real infrastructure for a real category, and it’ll be good at that category.

Just notice which tasks those are. They’re the ones where being nobody is not a handicap.

The other option is the tab you already have

Run the agent inside Chrome and the authentication question evaporates. Gmail is open. Notion is open. Your CRM is open. The agent reads the DOM you’re looking at, using the session you already established, with whatever MFA and device trust your IT team configured, and nothing about that has to be re-negotiated with a token, a service account, or a bot-detection vendor that flags datacenter IPs.

That’s what Dassi does. It’s a Chrome extension in the side panel, it sees what you see, and it acts in the tab you’re already authenticated in. No credential vault, no OAuth scopes to approve, no session replication. You point at the page and say what you want done. We’ve argued the same thing at more length in cloud browser agents can’t see your tabs.

There’s a real cost to the local approach and I’m not going to pretend otherwise: it doesn’t scale to a thousand parallel sessions, and your laptop has to be awake. Dassi is not going to crawl 40,000 product pages overnight. Kitesurf will.

Two different jobs wearing the same word

“Browser for AI agents” now describes both a fleet of anonymous edge instances and an extension riding your logged-in session, which is confusing enough that I expect a year of people picking the wrong one, discovering their agent can’t open Workday, and concluding that browser agents don’t work.

They work. Yours just needs to be somebody.

Dassi is free, runs on your ChatGPT subscription or your own API key, and keeps your page data between your browser and whichever model you picked. The agent that already knows who you are has a considerable head start on the one meeting you for the first time every session.