Claude in Chrome
Out of the app window——
Cowork moves into the browser.
On August 12, 2026, Anthropic upgraded its Chrome extension, "Claude in Chrome," into a full client for Claude Cowork, which had until now been limited to the desktop app. Open the side panel, and skills, plugins, and connectors just work. The need to switch windows is gone.
The Bottleneck
Switching windows was
a quiet drag on the work
Cowork is the mode where Claude handles several tasks on a user's behalf in parallel — a kind of working partner. But until now it was desktop-app only. If you wanted to hand it something while working in a browser, you had to step away and reopen the desktop app's window. That back-and-forth seemed minor, but it added up into real friction the more you used it day to day.
That changed on August 12, 2026. Anthropic upgraded the Chrome extension "Claude in Chrome" — until then a standalone browsing aid — into a full client for Cowork, as 9to5Mac reported. According to The Decoder's coverage, skills, plugins, and connectors that previously only worked in the desktop app now work in the browser too, with no extra setup required.
| Before: Desktop-only Cowork | After: Cowork in Chrome |
|---|---|
| Had to reopen the desktop app to use it | Called directly from the Chrome side panel |
| Skills and plugins worked in the app only | Work in the browser with no extra setup |
| Conversation history split across app and browser | Sessions persist across devices |
| Internal systems required an API/MCP connector | Can be operated directly through the browser |
How It Works
A session picks up
from either window
Start a task on desktop and continue it in Chrome, or vice versa — the key is session sync.
The extension becomes Cowork's official client
The previously standalone "Claude in Chrome" extension can now pick up a Cowork session directly. Conversations in the Chrome side panel are treated as part of the user's history too.
Skills, plugins, and connectors work in the browser
The same extensions available in the desktop app become active in the browser with no extra setup — no need to rebuild connections from scratch.
Move freely between desktop and browser
A task started in the desktop app can be continued in Chrome, or work started in Chrome can be finished on desktop.
Availability
Max and Team
get it first
Max and Team subscribers can use the new Cowork client starting on the announcement day itself, August 12. According to Dataconomy's report, access for the Pro plan is coming "in the coming weeks," meaning it wasn't opened to every user at once. The staged rollout can also be read as Anthropic being cautious about expanding this new scope of permissions — letting Claude carry out tasks inside the browser.
Who It Helps
Who benefits,
and how
The core shift: any internal tool you simply log into in a browser can now be something Claude operates directly.
Engineers: skip writing a dedicated connector
Internal dashboards and legacy admin panels that have no API/MCP connector can now be operated by Claude directly through the browser, cutting the cost of building and maintaining one-off connectors.
Business users: vendor portals work as-is
Internal and external tools you just log into with an ID and password — expense systems, CRMs — become something Cowork can operate once the extension is open, making routine browser-bound work easier to delegate.
PMs: keep a task from stalling
Ask the desktop app to research something before a meeting, then check on it or give further instructions from a browser on another PC while traveling. Because the session syncs, there's less need to write a separate handoff note.
Many of the tools people use every day already connect to Claude.
But plenty of others still don't.
What's Next / Risk
What comes next,
and what to watch
Only Max and Team subscribers can try this today. If that's you, start by updating the Chrome extension and confirming that conversations in the side panel actually sync with the desktop app's history. If you're considering connecting internal systems, it's worth auditing beforehand whether an existing API/MCP connector or this browser route offers easier permission control — that groundwork will make the transition smoother.
At the same time, letting Claude operate internal dashboards or vendor portals directly through the browser can blur permission boundaries more than a dedicated connector would. As The New Stack notes, a design where sessions persist across devices is also, by the same token, a design that keeps an AI agent touching screens that stay logged in. Pro-plan users don't have access yet, which is a reasonable window to stress-test the permission model before pushing for a company-wide rollout.