What is the built-in browser in Claude Cowork?

It is a browser Anthropic ships inside the Claude desktop app, launched in late August 2026. It runs in a side panel and lets Claude navigate sites, read pages, click elements, type into forms and complete web tasks without routing through the user's own Chrome install. Anthropic's framing was that most web tasks don't need your browser, just a browser.

Do I still need the Claude in Chrome extension?

Not for most tasks. Before this launch, giving Claude web access inside Cowork meant installing the Claude in Chrome extension and handing Claude control of your actual browser session. The built-in browser removes that dependency for general web work. The extension remains relevant when a task genuinely requires your live browser profile and its existing logged-in state.

Who can use Claude's built-in browser?

It is rolling out incrementally to Claude Pro, Max, Team and Enterprise plans as of late August 2026. It requires the Claude desktop application to be installed, open and online — even when the Cowork session itself is running in the cloud, because the browser executes locally through the desktop app.

Can Claude use my existing logins in the built-in browser?

Optionally. You can import saved credentials from Chrome, Edge and Firefox. Anthropic excludes highly sensitive categories such as banking and email logins from import by default. That default is the single most important security setting in the feature — importing broadly gives an autonomous agent standing access to any site you have saved.

Quick Answer

What Is Claude Cowork's Built-In Browser? (August 2026)

Published: August 31, 2026

The Short Answer

What: A browser built directly into the Claude desktop app, operating in a side panel, launched late August 2026 (reported around August 26–28).

Why it matters: It removes the Claude in Chrome extension as a prerequisite for web tasks in Cowork.

Who gets it: Pro, Max, Team and Enterprise, rolling out incrementally.

Requirement: Claude desktop app installed, open and online — even for cloud Cowork sessions.

Last verified: August 31, 2026.

The Strategic Point

Anthropic’s own phrasing in the announcement was the giveaway: “a lot of web tasks don’t need your browser, just a browser.”

That sentence is aimed squarely at Google. Until this release, Claude’s path to the live web ran through a Chrome extension — meaning Anthropic’s agent product depended on a Google-distributed runtime, subject to Google’s extension policy, in a browser Google controls. Shipping its own browser surface removes that dependency.

The move also lands in the same quarter that OpenAI shut down its standalone Atlas browser and folded browsing into ChatGPT Work’s built-in browser instead. Both labs converged on the same conclusion within weeks of each other: the agent doesn’t need to be a browser product, it needs a browser component. Standalone AI browsers asked users to switch daily drivers. Embedded browsers ask for nothing.

How It Works In Practice

The browser appears as a side panel next to the Cowork conversation. Claude drives it directly — navigating URLs, reading rendered page content, clicking elements, filling and submitting forms — and reports back into the same thread.

The architecture has one non-obvious property worth understanding: the browser is local even when the session is not. A Cowork session running as a cloud task still routes its browsing through your desktop app. Close the app and web-dependent work stalls. This is a deliberate trade — it means pages are fetched from your network and your IP, which keeps geo-restricted and IP-allowlisted content reachable, but it also means the feature is not truly headless.

Credential import

You can import saved logins from Chrome, Edge and Firefox. Anthropic excludes banking and email by default.

That default deserves respect rather than dismissal. Email in particular is the master key to nearly every other account through password reset — an agent with email access and a prompt-injection vulnerability is an account-takeover engine. Keep the exclusion.

The Security Model You Are Accepting

An agent-driven browser with imported credentials satisfies all three legs of what Simon Willison calls the lethal trifecta:

Leg	Present here?	Via
Access to private data	✅	Imported logins, local files, conversation history
Exposure to untrusted content	✅	Any web page Claude renders
An exfiltration path	✅	The browser itself — Claude can navigate anywhere

This is not a criticism unique to Anthropic; it is structurally true of every agentic browser shipped in 2026, including ChatGPT Work’s and Cloudflare’s Kitesurf. A web page can contain instructions addressed to the agent, and the agent has no reliable way to distinguish page content from user intent.

Practical mitigations that actually work:

Import narrowly. Only credentials for sites you specifically need agent access to. Never email, never banking, never your identity provider.
Use a dedicated browser profile for agent work rather than importing from your primary profile.
Watch the panel on first runs of any new task shape. The side panel exists partly so you can.
Assume anything visible to the agent is exfiltratable and scope credentials accordingly.

Where It Sits Against The Alternatives

Cowork’s browser is best understood as the convenience option: zero setup, tied to a subscription you already pay for, good enough for research, form-filling and multi-site data gathering. It is not a substitute for a hardened automation stack, and it is not designed for unattended production runs — the desktop-app dependency alone rules that out.

For a side-by-side against ChatGPT Work’s browser and the agent-native alternatives, see our agent browser comparison.