Claude Cowork Gets a Built-In Browser: Web Tasks Without an Extension

Claude Cowork now has a built-in browser in the desktop app. In an approved Claude post on X, Anthropic says the browser opens in Cowork's side panel when a task involves a website, allowing Claude to navigate, fill forms, and finish the web portion of the job.

This is a separate browser, not a new mode for taking over your existing tabs. Anthropic's official announcement says the built-in browser can read pages, click, and type without an extension or access to your own browser by default. That makes it useful when Claude needs a browser, rather than the particular page and login session already open on your machine.

Key Takeaways

• Cowork gets its own browser inside the Claude desktop app.
• No extension is required for the built-in browser.
• Claude can read, click, type, and fill forms in the side-panel browser.
• Your own tabs, bookmarks, and passwords stay separate unless you choose to bring a login over for a supported site.
• Pro, Max, and Team rollout: Anthropic says the feature is rolling out this week.
• Enterprise: Admins can turn the feature on for their organization.
• Desktop boundary: The built-in browser lives in the desktop app; web and phone access still depend on the desktop app being open for this capability.

A Browser for Tasks That Need the Web

The built-in browser targets a gap between connectors and browser extensions. A connector can provide a structured integration for a supported service, while Claude in Chrome can work through the tab you already have open. Cowork's new browser is for the middle case: a task needs a website, but it does not need your existing tab or browser profile.

Anthropic's examples include gathering research for a report, collecting invoices from a vendor portal, pulling numbers from a dashboard, and working through a portal with no connector. Claude opens its browser in the side panel, stays in the Cowork task, and handles the web steps while you keep working in the desktop app. (Anthropic's Cowork browser announcement)

The workflow can look like this:

1. Give Cowork a task that includes a website.
2. Cowork opens the built-in browser in its side panel.
3. Claude reads the page and navigates through the required steps.
4. Claude clicks, types, or fills a form as part of the task.
5. You review the resulting work and any consequential action before it is finalized.

The announcement does not turn every website into a reliable or fully automated integration. It adds a browser surface that can be used when a connector is unavailable, while leaving the user responsible for deciding which sites and actions are appropriate.

Built-In Browser vs. Claude in Chrome

Anthropic now offers two distinct browser workflows in its Claude apps:

The built-in browser is separate from your browser. Anthropic says it does not see your tabs, bookmarks, or passwords by default. You can bring logins over site by site from Chrome, Edge, or Firefox on macOS, and from Firefox on Windows and Linux, but that is an explicit choice rather than an automatic transfer. (Anthropic's Cowork browser announcement)

Claude in Chrome remains the better choice when the task depends on the tab you already have open, your existing login, or a browser workflow that you do not want to reproduce inside Cowork. Anthropic's separate Claude in Chrome general-availability announcement says that Chrome workflow is now generally available on every paid Claude plan.

The distinction is useful in practice: use Cowork's browser for a clean, task-specific web session, and use Chrome when the browser state itself is part of the work.

Rollout and Desktop Boundaries

Anthropic says the built-in browser is rolling out to Pro, Max, and Team plans in the Claude desktop app. The announcement describes the desktop rollout as covering macOS, Windows, and Linux, with Linux still in beta. On Enterprise plans, administrators can turn the feature on for the organization from the Cowork settings. (Anthropic's Cowork browser announcement)

This is separate from the X post about Claude in Chrome being generally available on all paid plans. The built-in Cowork browser and Claude in Chrome have different rollout language and different browser boundaries; do not treat the Chrome announcement as proof that the Cowork browser is available in every paid-plan surface.

The built-in browser lives in the desktop app. Anthropic says Claude can still drive it from the web or phone while the desktop app is open and online. Without the desktop app, Claude in Chrome remains the browser route for web work from the web surface. (Anthropic's Cowork browser announcement)

Logins and Sensitive Sites

The separation from the user's browser is a privacy and workflow boundary, but it is not a reason to treat browser actions as risk-free. The built-in browser can work through pages, forms, and portals, so the task may still involve sensitive information or consequential changes.

Anthropic says logins can be brought over site by site, while banking, email, and single sign-on sites are excluded unless the user chooses to include them. The company also calls out the same prompt-injection risk that applies to browser-using agents: a malicious instruction hidden in a page can try to redirect Claude away from the task. (Anthropic's Cowork browser announcement)

A sensible first run is a low-stakes site with a bounded task. Keep the browser separate from the accounts and tabs you use for unrelated work, review what Claude is about to submit, and avoid treating a successful research task as proof that an irreversible action is safe to delegate.

A Practical First Test

Try a task that benefits from a browser but does not require a sensitive login: collect the public specifications for several products, compare the numbers, and ask Cowork to organize the result into a report. Confirm that the side-panel browser opens, check the pages Claude visited, and review the citations before using the report.

For a signed-in workflow, bring over only the site needed for the task and use the narrowest permissions available. The built-in browser is most useful when it reduces setup without quietly expanding the scope of the task to every account in your regular browser.

Bottom Line

Claude Cowork's built-in browser gives the desktop app a separate web surface for tasks that need navigation, reading, clicking, typing, or form filling. It removes the need for an extension in those cases and keeps the user's normal tabs and browser profile separate. The rollout is aimed at Pro, Max, and Team users, with Enterprise admin controls, while Claude in Chrome remains the right choice for work that depends on the user's existing tab and login context.

Sources

• Claude on X, “Claude now has its own built-in browser in Cowork,” August 26, 2026: https://x.com/claudeai/status/2092755571455758427
• Claude on X, “Claude in Chrome is now generally available on all paid plans,” August 26, 2026: https://x.com/claudeai/status/2092755574563741871
• Anthropic, “Claude Cowork gets a built-in browser: nothing to install”: https://claude.com/blog/cowork-built-in-browser/
• Anthropic, “Claude in Chrome is generally available”: https://claude.com/blog/claude-in-chrome-generally-available