claude-news9 min readBy Rohit Mote

Claude Cowork Gets a Built-In Browser: Full Guide (2026)

Anthropic shipped a built-in browser for Claude Cowork on Aug 26, 2026. Here's what it does, how it differs from Claude for Chrome and Claude Code's browser, and how to use it safely.

Claude Cowork Gets a Built-In Browser: Full Guide

On August 26, 2026, Anthropic quietly shipped one of the more consequential updates to Claude Cowork this year: a browser that lives inside the desktop app, with nothing to install and no personal browser required. Claude can now open a website, read what's on the page, click through multi-step flows, and fill in forms — all inside its own sandboxed pane, while you watch.

If you've been running Cowork tasks that stall the moment Claude needs to touch a website — pulling invoices from a vendor portal, checking a competitor's pricing page, gathering research from a dozen tabs — this closes that gap without asking you to hand over your actual Chrome profile. Here's exactly what shipped, how it's different from the two other Claude browser features already out there, and how to start using it today.

What the Built-In Browser Actually Does

Claude Cowork's built-in browser is a dedicated, sandboxed browser instance that ships with the Claude desktop app. Instead of relying on your personal Chrome, Edge, or Firefox — or asking you to install a separate extension — Claude opens its own browser window to complete web-based steps of a task.

Concretely, it can:

  • Navigate to any URL and read the fully rendered page, including JavaScript-heavy dashboards that a simple scraper would fail on
  • Click through multi-step flows — logging into a portal, paging through a table, submitting a form
  • Extract structured data from pages, like pulling line items off an invoice or pricing off a comparison page
  • Fill out forms on your behalf as part of a larger Cowork task, while you watch each step happen live in the side panel

Anthropic frames the core use case plainly: "Claude opens its own browser to navigate sites, read pages, and fill forms, inside the desktop app." The intent is for web-based subtasks — research gathering, vendor portal lookups, dashboard extraction — to happen without you ever switching windows or babysitting a copy-paste loop.

The Login Import Detail That Matters

The feature includes a narrow but important capability: Claude can import your saved logins site-by-site from Chrome, Edge, or Firefox, so it doesn't have to work with a blank, logged-out browser for every site you actually use. But Anthropic built in a hard boundary here — sensitive categories are excluded by default. Banking, email, and single sign-on (SSO) providers are not imported unless you explicitly add them yourself. That's a deliberate trade-off: convenience for routine work portals, without quietly handing an agent the keys to your financial accounts or inbox.

Rollout: Who Gets It and When

The rollout is staged by plan:

PlanAvailability
Pro, Max, TeamRolling out the week of August 26, 2026 on macOS, Windows, and Linux (beta)
EnterpriseAvailable immediately — admins enable it via Organization settings → Cowork → Built-in browser

For Enterprise specifically, there's a timing detail worth flagging if you manage a workspace: the built-in browser is off by default at launch, but Anthropic has confirmed it will flip to on by default starting September 10, 2026, unless an admin has explicitly turned it off before then. If your org relies on Cowork and you want to review the feature before it auto-enables, that gives you roughly two weeks to make a call.

How This Compares to Claude's Other Browser Features

This is now the third distinct browser-related capability Anthropic has shipped for Claude in 2026, and they solve different problems. Confusing them will lead to picking the wrong tool for the job.

Claude Cowork built-in browser (Aug 2026)Claude Code built-in browser (Jul 2026)Claude for Chrome (May 2026)
Where it runsSandboxed browser inside Cowork desktop appSandboxed pane inside Claude Code desktopYour actual Chrome browser, as an extension
Session stateCan import specific site logins, excludes sensitive accounts by defaultStateless by defaultUses your real, logged-in Chrome sessions
Best forEnd-to-end Cowork tasks that need to touch external web portalsDocs lookup, design comparison, testing flows mid-coding-taskAutomating work across apps you're already logged into
Typical triggerPart of a broader Cowork task you assignAutomatic, when Claude needs to check something while codingExplicit, when you ask Claude to act in your browser
IsolationSandboxed from personal browsing data (except imported logins)Fully sandboxedShares your real browser profile and cookies

If you're a developer using Claude Code and want it to check documentation or compare a rendered UI against a design mock mid-task, that's the Claude Code browser — not this one. If you want Claude to act inside your actual logged-in Gmail, Notion, or project management tools using your existing session, that's Claude for Chrome. The new Cowork browser sits in between: it's for task automation that needs the open web, without giving an agent your entire browser identity.

Safety Controls: What Anthropic Actually Built In

Anthropic is explicit that the built-in browser uses the same prompt-injection defenses as Claude for Chrome, including safeguards that review Claude's actions against what you originally asked for before it proceeds. That matters because browser-using agents are one of the highest-risk categories of AI automation — a malicious or compromised webpage can, in theory, try to hijack an agent's instructions mid-task (a technique often called prompt injection).

Anthropic's own language on this is worth quoting directly, because it's unusually candid: these measures "meaningfully reduce the risk but can't eliminate it." Their recommendation is to start with trusted websites rather than pointing the browser at unfamiliar or untrusted domains for sensitive tasks.

Practical guidance if you're rolling this out for yourself or a team:

  • Start with internal or well-known vendor sites — invoicing portals, SaaS admin dashboards, documentation sites — before pointing it at arbitrary public URLs.
  • Don't import SSO or email logins just because the option exists. The default exclusion is there for a reason; only add exceptions deliberately.
  • Watch the first few runs of any new automated flow. The side panel shows Claude's actions live — use that visibility instead of walking away mid-task.
  • For Enterprise admins, treat the September 10 default-on date as a deadline, not a footnote. Review which teams use Cowork and decide your org's stance before it flips automatically.
  • Practical Use Cases Worth Trying First

    Based on how Anthropic is positioning the feature, these are the highest-value places to start:

    • Vendor invoice collection — Point Cowork at a recurring vendor portal and have it pull and organize new invoices instead of a human logging in monthly.
    • Competitive research sweeps — Ask Claude to visit a list of competitor pages and summarize pricing, feature, or messaging changes since your last check.
    • Dashboard data extraction — Pull metrics out of a third-party analytics or ad platform dashboard that doesn't have a clean API you already use.
    • Multi-step form submission — Automate routine form-based workflows (vendor onboarding forms, compliance questionnaires) where the steps are repetitive but the portal has no API.

    None of these require you to hand over your primary browser identity, which is exactly the gap this release fills.

    How to Turn It On

    If you're on Pro, Max, or Team and don't see it yet, it's a staged rollout through the week of August 26 — check back if it hasn't appeared. Once it's live:

  • Open Claude desktop and start (or continue) a Cowork task.
  • When Claude needs to do something web-based, it will use the built-in browser automatically, opening it as a visible pane.
  • To manage which browser Claude prefers, go to Settings → Cowork → Preferred browser. If you already use Claude for Chrome, that remains your default — the built-in browser doesn't override it unless you switch.
  • For Enterprise, an org owner needs to enable it first under Organization settings → Cowork → Built-in browser, and can review or add exceptions to the login-import exclusion list before rollout.
  • Key Takeaways

    • Claude Cowork's new built-in browser (shipped August 26, 2026) is a sandboxed browser inside the desktop app — no install, no personal browser required.
    • It can import specific site logins but excludes banking, email, and SSO accounts by default; you must explicitly add exceptions.
    • It's distinct from Claude Code's built-in browser (July 2026, for dev workflows) and Claude for Chrome (May 2026, which uses your real browser session).
    • Enterprise admins get a roughly two-week window before the feature switches to on-by-default on September 10, 2026.
    • Anthropic is upfront that prompt-injection defenses reduce but don't eliminate risk — start with trusted sites.

    Next Steps

    If you're prepping for a Claude-focused role or the Claude Certified Architect (CCA) exam, staying current on releases like this one is exactly the kind of applied knowledge the certification tests — not just prompt syntax, but how Anthropic's product surface (Claude.ai, Cowork, Code, and the platform) fits together and where the safety trade-offs sit. Check out AI for Anything's CCA practice test bank to work through scenario-based questions built around real Claude product behavior, or browse our free study guides to keep pace with Anthropic's release cadence heading into exam day.


    Sources:
    R

    Rohit Mote

    Founder, AI for Anything

    Rohit Mote is the founder of AI for Anything and builds AI-powered products full-time across the Infinite Products Machine portfolio. Every guide is grounded in hands-on daily use of Claude, Claude Code, and the broader AI tool ecosystem in production systems.

    How we create and review our guides →