Claude Cowork Built-In Browser: Side-Panel Web Agent (Aug 2026)

On August 27, 2026 at 4:56 AM, Claude (@claudeai) posted:

Claude now has its own built-in browser in Cowork. When your task involves a website, a browser opens in Cowork's side panel, and Claude navigates, fills forms, and finishes the job.

The demo video hit 531K+ views. Two follow-up posts clarified the product split Anthropic is shipping this week:

1. Cowork browser — built into the desktop app, separate from your browser and logins, rolling out over the next week on all paid plans
2. Claude in Chrome — generally available on all paid plans for users who want Claude in their own browser where they are already signed in

Also August 27: OpenAI documented the other side of this browser-agent choice. ChatGPT Work's cloud browser can now pause for secure sign-in and retain its own authenticated session for later tasks, while keeping that session separate from the user's personal browser.

For builders tracking the browser-agent arms race, this is Anthropic completing the loop: July shipped browsing inside Claude Code for developers; August 27 ships it inside Cowork for everyone else doing web-shaped knowledge work.

TL;DR — two browsers, one week

What Cowork's browser actually does

Anthropic's demo pattern: you assign a web task in Cowork → a browser pane opens beside the chat → Claude navigates, reads, clicks, fills forms → returns output into the Cowork workflow (files, scheduled task, skill, etc.).

That matches use cases explainx.ai already saw in the wild — Search Console SEO browser ops, lead research, reporting dashboards — but removes the "install Claude in Chrome first" friction for users who only live in the desktop app.

Architectural choice: sessions stay separate from your personal browser. Cowork does not inherit your Google login, bank SSO, or extension blocklists. Trade-off: Claude cannot act inside your authenticated Notion workspace unless you switch to Claude in Chrome or use a connector.

Cowork browser vs Claude in Chrome vs Platform computer use

Anthropic now covers both browser models consumers argue about:

• Sandboxed agent browser (Cowork) — safer credential isolation, weaker on "use my logged-in SaaS"
• Attended browser extension (Chrome) — stronger on authenticated workflows, larger prompt-injection blast radius

Safety — what changed, what did not

Changed: Cowork users get web automation without handing Claude their Chrome profile.

Unchanged: Browser agents on attacker-controlled pages remain a prompt-injection surface. Anthropic's Chrome safety docs already state the risk is not zero; Cowork's isolated browser reduces credential theft from shared sessions but not malicious page content.

Practical guidance from explainx.ai's Cowork safety guide:

• Use Cowork browser for public web + form fills on trusted domains
• Use Claude in Chrome when the task requires your login
• Never let either touch financial transactions or sensitive PII without human review
• Keep Cowork on a dedicated machine or folder scope for high-risk workflows

The SharedRoot sandbox escape (CVE-2026-46331) is a reminder that desktop agent blast radius includes filesystem paths Cowork can reach — browser isolation does not replace folder scoping.

What people are asking

"Wait — Cowork didn't already have a browser?"

Fair reaction on X. Claude in Chrome existed in beta since early August, and power users routed web work through the extension. What changed August 27 is a native pane inside Cowork itself — no Chrome install, no extension permissions dialog, no dependency on Google’s release channel. Cowork can now spawn web context as part of a scheduled task or folder job without leaving the desktop app.

"Why two browsers instead of one?"

Anthropic is drawing a session boundary:

Merged sessions would be convenient and dangerous — one poisoned page in a shared profile could affect both automation and your personal Gmail.

"Does this burn more Cowork credits?"

Anthropic did not publish per-browser pricing in the launch thread. Browser steps add tool rounds (navigation, screenshots, form fills) on top of text generation. Users already reporting Pro credit burn on Cowork schedules should expect web-heavy tasks to cost more than folder-only summaries. Test one workflow manually before automating daily.

"How is this different from ChatGPT's browser / agent mode?"

X replies compared Anthropic to OpenAI’s earlier browser tooling. The architectural difference explainx.ai tracks: Cowork browser is sandboxed in-app; Claude in Chrome uses your real profile. OpenAI’s consumer browser agents historically mixed those models differently week to week. Anthropic’s August 27 message is explicit: pick isolated agent browser OR authenticated extension — not one confused middle ground.

Workflows that get easier with Cowork browser

These patterns from real Cowork use cases previously required Claude in Chrome or manual copy-paste:

None of these eliminate human review for consequential submissions — insurance forms, legal filings, payments. The browser automates navigation; you keep approval gates.

Decision guide — which browser this week?

Does the task need a site where you're already logged in?
├── YES → Claude in Chrome (GA on paid plans)
└── NO  → Cowork built-in browser
         ├── Scheduled Cowork task? → built-in browser (no Chrome dependency)
         └── One-off chat in claude.ai web? → still use Chrome extension if installed

Developers in Claude Code — ignore this guide; stay on Cmd+Shift+B in-app browser for localhost and docs.

Teams building custom agents — neither Cowork nor Chrome replaces Platform browser use in your VPC; these are Anthropic-hosted product surfaces.

How Cowork browser fits Anthropic's August stack

The browser launch lands in a dense product month:

Together: memory (what Claude knows about your project) + browser (how Claude acts on the web) + skills/connectors (how Claude touches files and SaaS APIs). The browser was the missing leg for users who refused to install Chrome extensions on managed corporate laptops.

Rollout — what to do this week

1. Update the Claude desktop app to the latest build
2. Confirm paid plan — rollout is all paid tiers, not free
3. Open Cowork → assign a low-risk web task (public FAQ page, read-only research)
4. Watch for side panel — Anthropic says rollout spans ~one week from Aug 27
5. If you need logged-in SaaS, enable Claude in Chrome — now GA, remains default if already configured
6. Document which workflows use which browser for your team — mixed setups confuse audit trails

If the pane does not appear by early September 2026, check Anthropic status and plan release notes — staged rollouts often hit Max/Team before Pro.

Limitations worth knowing

• No mobile Cowork browser in the August 27 announcement — desktop app only
• CAPTCHA and bot detection — same class of failures as Warmwind-style web automation; sandboxed browser does not magically bypass anti-bot systems
• HIPAA / regulated orgs — Claude in Chrome explicitly excludes some healthcare deployments; Cowork browser inherits similar enterprise policy constraints — verify with Anthropic before clinical workflows
• Free tier — excluded from rollout; browser automation remains a paid capability

Bottom line

Claude Cowork's built-in browser closes the "junior assistant can't use the web" gap — the same week Claude in Chrome graduates from beta to GA. Anthropic is not picking one model; it is shipping two, with clear session boundaries.

If you already run Cowork schedules for digests and reporting, the side-panel browser is the missing piece for web-native steps. If your workflow is "Claude, fix this in my logged-in admin panel," keep Claude in Chrome as default.

Related on explainx.ai

• Claude in Chrome — features, access, and real risks
• Claude in Chrome cross-device sync
• Top 10 Claude Cowork use cases
• How to use Claude Cowork safely
• Claude Code desktop browser (July 2026)
• Claude Platform computer use GA
• Claude unified memory across Chat and Cowork
• Record a Skill — Cowork screen recording

Official: @claudeai launch post · Cowork built-in browser blog · Claude in Chrome GA blog

Rollout timing reflects Anthropic's August 27, 2026 posts. Feature availability may vary by plan and region — check the desktop app after updating.