What jumped out at me isn’t that Claude got a browser. It’s that Anthropic is now treating “the browser” as something it can inline, hide in a side panel, and switch on by default without making a big philosophical speech about the open web. That’s a very product-y move. Maybe even a little too product-y.
I actually think the interesting part here is the admission that most web work does not need your browser state at all. That line lands because it’s true for a lot of agentic tasks: fetch pages, compare sources, extract public data, maybe navigate a few clicks. The moment you need logins, though, the whole story gets messier fast. Anthropic is being careful about that, which is sensible, but also a reminder that this is a browser only in the limited sense that matters for demos.
The DMA angle is clever, and a bit cheeky. If the browser lives inside Claude and never really becomes a browser choice on the user’s machine, then the whole “choice screen” regime doesn’t bite. That doesn’t sound like a legal violation to me from the article’s description, but it does underline the gap between regulation and product design. Europe asked for an explicit selection moment; the industry response is to bury the moment inside an app flow where nobody is making a conscious “browser” decision at all.
I’m also not convinced the security framing is as tidy as it sounds. Anthropic says prompt injection is still a risk, and that’s the right level of honesty. But if the same class of attack already applies in the Chrome-extension model, then swapping the browser substrate doesn’t magically solve much. It may even lull people into thinking the risk has been engineered away when it really hasn’t. If I were evaluating this for actual internal use, I’d want to know exactly what the guardrails do and where they fail under hostile pages.
What I’d try first is boring: public research tasks, price checks, document lookups, maybe gathering citations from a list of URLs. Not “let Claude roam my accounts.” The line between useful agent and dangerous proxy is still very thin, and Anthropic knows it. This reads less like a breakthrough than a sign of where the whole category is headed: more built-in browsing, more defaults, and fewer moments where the user explicitly opts in to the machine acting on the web.
Reference: Claude now has its own browser and no longer needs the Chrome extension
