Cowork browser capability is the quietest but most consequential thing Anthropic has shipped this summer, and on 12 August 2026 it took its clearest step yet. The company turned the Claude in Chrome side panel into a full Claude Cowork session, so a task you begin in a browser tab now continues on the Claude desktop app without losing its history, its skills or its connectors. Read alongside the sandboxed browser Anthropic put inside Claude Code on the desktop in July, the direction is unmistakable: Anthropic wants a browsing surface it controls, wired directly into the agent.
That matters because the browser has become the bottleneck for agentic work. An assistant that can read your files but cannot open a supplier portal is only half useful. A dedicated Cowork browser closes that gap, and it changes the risk calculation for every business weighing up whether to let an autonomous AI agent act on live systems. This article sets out precisely what has shipped, what a dedicated Cowork browser would add on top, how the current browsing options compare, and what your team should do before switching any of it on.
Table of contents
- What Anthropic has actually shipped so far
- Inside the Cowork browser: extension versus dedicated window
- Why a Cowork browser matters for cross-device sessions
- The Cowork browser security question
- Cowork browser availability, plans and rollout
- What a Cowork browser changes for UK businesses
- How to prepare your team for the Cowork browser
- Frequently asked questions about the Cowork browser
- References
What Anthropic has actually shipped so far
Two separate pieces of work are converging, and conflating them is where most of the confusion around the Cowork browser comes from. The first is a genuine in-application browser. The second is a session model that makes browsing portable.
The in-app browser inside Claude Code
In July 2026, as part of the versions 2.1.202 to 2.1.206 update run, Anthropic shipped a built-in web browser inside Claude Code on the desktop. Anthropic’s own framing was that Claude “can pull up docs, designs, or any other site” and “read, click through, and interact the same way it does with your local dev servers.” It launches with a clean profile: no saved logins, no browsing history, and no inherited cookies from your everyday browser.
That profile design is the important part. It is sandboxed and stateless by default, though developers can choose whether browsing sessions persist between runs. It is the closest thing to a dedicated Cowork browser that exists in the desktop app today, even though Anthropic scoped it to the coding product rather than to general Cowork sessions.
The Chrome side panel becoming a Cowork session
The second piece landed on 12 August 2026. Until then, the Claude in Chrome side panel ran a conversation that was walled off from the Claude apps, so nothing carried across. Now the side panel runs the same Cowork session you use everywhere else. Conversations save to your history, your skills and connectors work without reconfiguration, and the session lives with your account rather than with one device.
Anthropic’s worked example is a finance one: ask Claude to gather invoice amounts and dates from several vendor portals, let it open the tabs, read each invoice and build a spreadsheet, then pick the same session up in the desktop app to add files from your computer. That handover is what makes a Cowork browser useful rather than novel.
Why the desktop app remains the privileged surface
Anthropic’s own support documentation is blunt about the hierarchy. Desktop is the full experience: tasks, connectors, skills, scheduled tasks, projects, live artifacts, local file access, browser use and computer use. Web and mobile support task creation, session resumption, connectors, skills, file previews, scheduling and projects, but exclude live artifacts and direct browser or computer control.
There is a hard dependency buried in that split. A cloud session can read and write files in folders you have connected on your computer only while the desktop app is open. Close the laptop and the session keeps running, but it cannot reach your local files. Any Cowork browser strategy has to account for that.
Inside the Cowork browser: extension versus dedicated window
The practical question for most teams is not whether Anthropic ships a dedicated Cowork browser, but which browsing mode to use for which job. The two models solve genuinely different problems, and picking the wrong one is how organisations end up with either a useless agent or an over-permissioned one.
The extension model borrows your identity
Claude in Chrome sees the page you are on and acts inside it — clicking links, typing text, navigating between pages and completing forms — using your existing logins. That is enormously powerful for anything sitting behind authentication: a CRM, a supplier portal, an internal dashboard. It is also the mode where a mistake reaches straight into a system where you are already signed in as yourself.
The dedicated window model starts from zero
A dedicated Cowork browser inverts that. The profile is clean, so there are no ambient credentials to abuse, and anything the agent reaches is reachable by anyone. Anthropic’s guidance for the Claude Code implementation says exactly this: use the in-app browser for building, testing and sites that do not require authentication, and reach for the extension when Claude needs to act as an authenticated user.
How to choose between them
| Factor | Dedicated Cowork browser (in-app) | Claude in Chrome extension |
|---|---|---|
| Starting profile | Clean, no saved logins | Your live browser profile |
| Browsing history | None inherited | Full personal history present |
| Session persistence | Off by default, configurable | Always persistent |
| Authenticated sites | Not the intended use | Primary use case |
| Blast radius of an error | Contained to the sandbox | Reaches every logged-in system |
| Best for | Research, docs, testing, public data | Portals, dashboards, internal tools |
The honest summary is that a dedicated Cowork browser is the safer default and the extension is the more capable one. Mature teams will run both and route work deliberately rather than treating the Cowork browser as a single switch.
Why a Cowork browser matters for cross-device sessions
Session portability is the feature that turns a browsing tool into an operating model. Before 12 August, work done in the side panel evaporated when you moved. Now the same Cowork browser session is available from wherever you next sit down.
Sessions live with the account, not the machine
Because a session belongs to your account, you can start a piece of work in a browser tab, close the laptop, and review or redirect it from a phone. Anthropic’s framing is that a task can begin on a desktop, continue in the background, and be checked from another surface entirely. For distributed teams that is the difference between an assistant and a colleague.
Where each surface can and cannot browse
| Capability | Desktop app | Web | Mobile | Chrome side panel |
|---|---|---|---|---|
| Create and run tasks | Yes | Yes | Yes | Yes |
| Resume a session started elsewhere | Yes | Yes | Yes | Yes |
| Connectors and skills | Yes | Yes | Yes | Yes |
| Scheduled tasks and projects | Yes | Yes | Yes | Yes |
| Live artifacts | Yes | No | No | No |
| Local file read and write | Yes | No | No | No |
| Local connectors and MCP servers | Yes | No | No | No |
| Browser control | Yes | No | No | Yes |
| Computer use | Yes | No | No | No |
Counting those nine capabilities gives a clean picture of why the Cowork browser question keeps pointing back at the desktop app.
The handover pattern worth designing around
The pattern that pays off is deliberate handover. Let the Cowork browser gather from external sources where the data lives, then move the session to the desktop app where local files, connectors and live artifacts are available. Teams that try to run everything in one surface end up fighting the capability split rather than using it.
The Cowork browser security question
No serious assessment of a Cowork browser can skip the attack surface, because giving an agent a browser gives it a channel into everything that browser can reach. Anthropic has been unusually direct about this rather than burying it.
Prompt injection is the unsolved problem
Anthropic acknowledges plainly that browser agents remain vulnerable to prompt injection, where instructions hidden in a web page hijack the agent’s behaviour. Its published advice is to start on sites you trust and to follow the safe-use guidance. That is a meaningful admission from a vendor with every commercial incentive to say the problem is solved, and it should shape how conservatively you scope any Cowork browser pilot.
What Anthropic built to contain it
Two controls sit around consequential actions. Before Claude submits a form, sends a message or downloads a file, a separate review checks the proposed action against what you originally asked for. On top of that, irreversible or costly actions — purchases, sharing personal data — still require your explicit approval. Enterprise administrators get a third lever: the browser integration is off by default and can be restricted to an approved list of domains.
Where your own controls have to fill the gap
Vendor controls stop obvious misuse; they do not replace governance. Anyone treating a Cowork browser as a cybersecurity-neutral productivity tool has misread it. Treat it as a new privileged identity on your network, and apply the same review you would to any tool that can act on live systems. The domain allowlist is the single highest-value control available, because it converts an open-ended risk into a bounded one.
A realistic pilot boundary
Start the Cowork browser on public research, documentation and read-only data gathering. Extend into authenticated portals only once you have logged a few weeks of real sessions, and keep purchase and payment flows out of scope entirely at first. That sequencing costs you very little capability and removes most of the tail risk.
Cowork browser availability, plans and rollout
Access is uneven right now, and that unevenness is temporary, so plan for the end state rather than today’s snapshot.
Who has the Chrome Cowork session today
The side panel Cowork session went live for Max and Team plans on 12 August 2026, with Pro rolling out over the following weeks. Enterprise availability depends on an administrator enabling it. Cowork itself is in beta on web and mobile for Pro, Max and Team plans, having launched in January 2026 as a macOS-only research preview restricted to Max subscribers.
How the browsing story arrived
Seven months separated the first Cowork preview from the first dedicated browser in the desktop app, and only 33 days separated that browser from full session portability. The compression is the signal.
The Windows cost nobody mentions
| Plan | Cowork access | Chrome Cowork session | Admin controls |
|---|---|---|---|
| Pro | Yes, beta on web and mobile | Rolling out | None |
| Max | Yes, full desktop experience | Live | None |
| Team | Yes, full desktop experience | Live | Limited |
| Enterprise | Admin-enabled | Off by default | Domain allowlist |
There is also a hardware footnote that matters for Windows fleets. Reporting from Neowin found that the Claude desktop app spins up a 1.8GB Hyper-V virtual machine once Cowork or agent mode has been used even once, and that it does so on every launch afterwards. On Windows 11 Home, where Hyper-V is unavailable, that has caused launch failures outright. Before you roll a Cowork browser out to a mixed estate, check the edition of Windows your users actually run.
What a Cowork browser changes for UK businesses
Strip away the product detail and the shift is straightforward: work that used to require a person to open tabs can now be delegated, with a reviewable trail, to an agent that never loses the thread between devices.
The processes that benefit first
Supplier price checks, invoice reconciliation across vendor portals, competitor monitoring, licence renewal tracking and regulatory reading are all high-volume, low-judgement browsing tasks. They are exactly the shape a Cowork browser handles well, and they are the tasks that quietly consume hours of skilled time every week.
Where the value actually lands
| Task type | Suited to a Cowork browser | Why |
|---|---|---|
| Public research and market scanning | Strong fit | No credentials needed, low blast radius |
| Invoice and statement gathering | Good fit with controls | Repetitive, but needs portal logins |
| Form filling in internal systems | Conditional | Requires approval steps and an allowlist |
| Purchases and payments | Not yet | Irreversible; keep a human in the loop |
| Handling special category personal data | Not yet | Injection risk outweighs the time saved |
What it does not replace
It is worth being clear about the limits, because vendor enthusiasm tends to blur them. A browsing agent does not understand your commercial context, does not know which supplier relationship is politically delicate, and cannot tell a genuine price change from a mispriced listing. It reads what is on the page. Every output still needs a person who knows the business to sanity-check it before anything is actioned, and the teams getting real value are the ones treating the output as a first draft rather than a decision.
There is a procurement point buried in there too. If a Cowork browser removes six hours a week of tab-clicking from a senior person, the saving is only realised if that time is redeployed deliberately. Otherwise it simply disappears into the working day, and the pilot reports a benefit nobody can find in the accounts twelve months later.
The comparison that actually matters
Measured against a browser extension bolted onto a chat window, a dedicated Cowork browser is a modest upgrade. Measured against the way most teams work now — a person, twelve tabs and a spreadsheet — it is a different category of tool. That second comparison is the one your business case should use, and it is the one that survives contact with a finance director.
How to prepare your team for the Cowork browser
Preparation is mostly governance, not engineering, and it can be done in a fortnight by an existing IT function.
Decide what the agent may reach
Write the domain allowlist before anyone runs a session, not after. List the sites the Cowork browser may open, the systems it may never touch, and the actions that always require sign-off. Keep the first version deliberately short; expanding a list is easy, and retracting one after an incident is not.
Fix the identity question early
Decide whether agent browsing happens as a named human or under a dedicated service identity. The extension model inherits whoever is signed in, which makes audit trails ambiguous. A separate account with narrow permissions costs almost nothing and makes every subsequent question about accountability answerable.
Train for the failure mode, not the feature
Users need to recognise one thing above all: a web page can contain instructions aimed at the agent rather than at them. Show a real example in training. A team that understands why the Cowork browser pauses for approval will use those pauses properly instead of clicking through them.
Establish a review rhythm
Sample sessions weekly for the first month, then monthly. Read what the agent actually did against what was asked. Most organisations discover that their real problem is not rogue behaviour but scope creep — a Cowork browser quietly being used for work nobody assessed.
Get your endpoint estate straight
Confirm which machines run Windows 11 Pro or Enterprise with Hyper-V available, which run Home, and which are on macOS. Confirm who has Max, Team or Pro. The Cowork browser rollout that fails is almost always the one where entitlement and endpoint capability were never mapped against each other. If your internal team is stretched, this is a sensible thing to hand to a managed IT services partner.
Frequently asked questions about the Cowork browser
Is there a standalone Anthropic browser I can download?
No. There is no separate browser product. The dedicated browsing surface exists inside the Claude desktop app, currently scoped to Claude Code, alongside the Chrome extension that now runs a full Cowork session.
Does the Cowork browser see my saved passwords?
The in-app browser starts from a clean profile with no saved logins or history, so it does not. The Chrome extension does operate inside your signed-in profile, which is exactly why it is the more powerful and more sensitive of the two options.
Can I stop staff using it?
On Enterprise plans, yes: the integration is off by default and administrators can enable it selectively and restrict it to approved domains. On individual Pro and Max plans there is no central control, which is a good reason to prefer Team or Enterprise for business use.
Does a Cowork browser session keep running if I close my laptop?
The session continues, but it loses access to local files the moment the desktop app is closed. Cloud-side work carries on; anything depending on your machine pauses until the desktop app is open again.
Which browsers are supported?
Chrome only for the extension at present. Other Chromium browsers and mobile browsers are not supported, so a Cowork browser deployment currently assumes a Chrome standard build or the desktop app. If your organisation has standardised on Edge or Firefox, the practical route today is the desktop app rather than the side panel.
How should we measure whether it is working?
Pick two or three repetitive browsing tasks, time how long they take a person today, and measure the same tasks after a month of Cowork browser use — including the time spent reviewing the agent’s output, which is the number most pilots forget to count. A saving that survives that honest accounting is real. One that only appears when review time is excluded is not, and it is far better to find that out in a pilot than in a renewal conversation.
Is this different from a general-purpose AI browser?
Yes, and the distinction is worth holding onto. Several vendors are shipping browsers with an assistant bolted into the chrome of the application. Anthropic’s approach runs the other way round: the agent is the product and the browser is a tool it picks up when a task needs one. That is why the Cowork browser conversation keeps returning to sessions, skills and connectors rather than to tabs, bookmarks and sync.
References
Claude Cowork comes to the Chrome side panel
Use Claude Cowork on web, desktop, and mobile
Get started with Claude Cowork
Claude’s Chrome side panel is now a full Cowork session
Anthropic highlights Claude Code’s in-app browser on the desktop
Anthropic’s Chrome extension is now a Cowork session
More AI coverage: explore Progressive Robot's AI Models, Tools & Releases hub — hands-on reviews, setup guides and benchmarks in one place.
