Claude gets its own browser in Cowork: Points: 1 # Comments: 0

What happened

The file is mostly HTML/CSS. Let me search for the actual article text content. I now have all the facts I need. Let me write the article.

Claude gets its own browser in Cowork

Anthropic published a blog post on August 26, 2026, announcing that Claude now has a dedicated built-in browser inside the Cowork desktop app. The browser opens sites, reads pages, clicks, and types on Claude's behalf while users keep working in the foreground. Nothing needs to be installed, and the browser is fully isolated from the user's own tabs, bookmarks, and passwords.

How it works

This piece covers what the feature does, how its isolation and login model work, what it means for people who already use Claude in Chrome, and which plans can access it. It is aimed at Cowork users, developers building on Claude, and enterprise IT administrators weighing the rollout.

Anthropic added a built-in browser to the Claude Cowork desktop app and began rolling it out across Pro, Max, and Team plans on August 26, 2026. On Enterprise plans the feature is available immediately, with admins able to manage it through Organization settings → Cowork → Built-in browser. For everyone else on supported plans the rollout is expected to complete within the coming week. Once the feature reaches a user, it is on by default: hand Claude a task involving a website and the browser opens on its own, without any configuration step.

The announcement frames the addition as a complement to, not a replacement for, the existing Claude in Chrome browser extension. The two tools serve different jobs. Claude in Chrome operates inside a browser the user already has open, using sessions the user is already authenticated to. The built-in browser handles tasks the user wants to delegate entirely — gathering research, pulling numbers from a dashboard, or working through a vendor portal that has no pre-built connector — while the user stays focused on something else.

Why it matters

The built-in browser is isolated from the user's personal browser. Claude never sees the user's tabs, bookmarks, or saved passwords. To keep Claude signed in to specific websites, users can import credentials site by site from Chrome, Edge, or Firefox on macOS, or from Firefox on Windows and Linux. Banking sites, email, and single sign-on services are excluded from that import by default and can only be included by an explicit user choice.

Users who already have Claude in Chrome installed keep it as their default. For users without that extension, the built-in browser becomes the default. Either way, the active preference can be toggled at any time in Settings → Cowork → Preferred browser. The browser lives inside the desktop app itself, but Claude can still drive it from the web or a phone as long as the desktop app is open and connected. The web interface without the desktop app continues to rely on Claude in Chrome.

Before this feature, giving Claude web access in Cowork required installing the Claude in Chrome extension and giving it access to the user's own browsing session. That approach works well when the task is already in front of the user in an open tab, but it means Claude and the user share the same authenticated context. A separate browser with its own session lets Claude take on tasks that do not need the user's accounts at all, reducing the surface area of what Claude can touch.

Who is affected

The isolation model also addresses a practical operational concern: many workflows involve portals or dashboards that have no API connector and no automation-friendly interface. The built-in browser lets Claude navigate those portals directly, filling forms and extracting data, without requiring the user to stay present or to expose their full authenticated session to the agent.

Pro, Max, and Team subscribers using the Claude desktop app on macOS, Windows, or Linux will receive the feature on a rolling basis over the week following August 26, 2026. Linux support is noted as being in beta. Enterprise plan customers and their admins have access from day one and can enable or restrict the feature organization-wide through the Cowork section of Organization settings.

Users who rely on Claude in Chrome are not displaced. That extension continues working and remains the default for anyone who has it installed. The built-in browser is the new default only for users who have never installed Claude in Chrome. Anthropic acknowledges that the built-in browser carries the same prompt injection risks as any AI agent operating in a browser, where instructions hidden in a page can attempt to redirect Claude's actions, and states that it runs the same safeguards as Claude in Chrome, including checks that review Claude's actions against what the user originally requested.

What to watch next

The Linux rollout is listed as beta, so builders targeting Linux deployments should verify behavior before relying on the feature in production workflows. Enterprise admins should confirm the Organization settings → Cowork → Built-in browser toggle is in its intended state before users encounter tasks that would invoke the browser automatically. Anthropic points to a safety guide on the Claude website for detail on how prompt injection safeguards work, which is worth reading before deploying Claude against internal portals or sites outside a controlled list.

Longer term, the distinction between the two browser modes — isolated built-in versus user-session Chrome extension — will be the clearest design decision to watch. The built-in browser currently requires importing credentials site by site, which is friction that Anthropic may reduce. Whether banking and single sign-on exclusions remain defaults or become configurable at the enterprise level is also an open question that admins on regulated plans should track.