The top post on Hacker News this morning is “OpenClaw is finally available on Android and iOS,” and the comment thread underneath it is doing that thing where everyone declares a new era before lunch. Agents in your pocket. Agents everywhere. One person called it “the year the assistant left the desk.” I read all of it while sitting at my desk, in Chrome, with about forty tabs open, most of them logged into things.

And that gap right there is the whole story.

The phone is not where your logins are

Here is what a mobile OpenClaw app can actually reach: whatever it can spin up inside its own sandbox, plus whatever accounts you re-authenticate on that device. It cannot reach the Gmail tab you’ve had open since March. It cannot reach the internal admin panel you logged into behind your company SSO an hour ago, the one with the session cookie that expires if you so much as sneeze at it.

Your actual work does not live on your phone. It lives in the browser on the machine where you already did the annoying part, the logging in, the two-factor dance, the “verify it’s you” email. That state is sitting there, warm and ready, and a separate app on a separate device is standing on the far side of a wall from it.

Everywhere is not the same as inside

Mobile availability is a distribution win. I don’t want to pretend it isn’t useful to poke an agent from a train platform. But “runs on more surfaces” and “can see my authenticated session” are unrelated properties, and the announcement collapses them into one vibe.

When an agent runs somewhere else, whether that’s a phone, a VPS, or some managed cloud browser, it starts every task as a stranger. It gets a fresh browser with no memory of you, so before it can do the thing you asked, it has to become you, which means credentials go somewhere, or a login flow gets triggered, or it just quietly fails on the page that only loads for signed-in users. We wrote about this exact blind spot in cloud browser agents can’t see your tabs, and going mobile doesn’t fix it. It arguably makes it worse, because now the agent is even further from your real session than a cloud instance sitting in the same datacenter as nothing you own.

What “browser-native” actually buys you

So run the agent inside the browser you’re already using.

That’s the entire pitch, and it sounds almost too small to matter until you watch it work. Dassi lives in the Chrome side panel and operates the page you have open, with the session you already established, using the cookies that are already there. No re-login. No token handoff. No cloud browser pretending to be you and getting caught at the door.

The difference shows up on the boring tasks, which is most tasks. Draft replies in the Gmail tab that’s authenticated as you. Pull the numbers out of an internal dashboard that would 403 any external agent. Fill the same six-field form you fill every Tuesday. When I asked an agent to work through my company’s billing portal, the version running in my own browser just did it, because it inherited the exact session I’d opened, while anything running elsewhere would have hit a login wall that no amount of cleverness gets past without my password. This is the part the “agents everywhere” framing keeps skipping, and it’s the part that decides whether the agent is useful or just present.

You can also swap the model underneath it whenever you want, which matters more than it used to now that a genuinely good model ships every few weeks. Log in with a ChatGPT subscription or bring your own key for Claude, Gemini, whatever. The plumbing stays local either way. There’s more on why that local execution beats a rented server in our take on OpenClaw and local browser execution.

The mobile app is real. So is the wall.

I’m not knocking OpenClaw for shipping mobile. It’s a real product doing a real thing, and a lot of people wanted it. What I’m skeptical about is the story wrapped around the launch, the one that treats “my agent is on more devices” as if it were the same sentence as “my agent can finally do my work.”

It can’t, not from over there. The session that matters is the one already open on your laptop, and no phone app reaches across that gap. A browser agent that runs right where you’re already logged in doesn’t have to. It’s already inside.

Anyway. My tabs are still open. Someone on that HN thread is now arguing the desktop is dead, which is a bold thing to post from a keyboard.