Claude in Chrome is no longer just a chat box beside a web page. Anthropic has rebuilt the Chrome side panel as a Claude Cowork session, so browser tasks can be saved, resumed and combined with the user's existing skills and connectors.
The practical shift is straightforward: Claude can read the active page, click, type, fill forms and move across tabs, while the same conversation can continue later in Claude Desktop, Claude Web or Claude Mobile. A task that starts in Chrome no longer has to stay there.
Your Claude in Chrome sessions now carry over to desktop, web, and mobile.
The side panel becomes a workflow
Anthropic's help material says Claude in Chrome is available across paid plans. Max and Team users get the Cowork side panel now, Pro is rolling out over the coming weeks, and Enterprise organizations need administrators to enable cloud Cowork before the side panel runs this way.
That makes the side panel more than a renamed extension. Its conversations appear in history, and configured skills, plugins and connectors work in the browser. 9to5Mac describes a typical use case: collecting invoice details from vendor portals, creating a spreadsheet, then continuing on desktop to add local files or compare a budget.
Automatic approval has limits
The browser extension asks for serious permissions, including scripting, debugger, tabs, downloads and webNavigation. The debugger permission is what lets Claude click, type and take screenshots; downloads lets it save files; webNavigation helps identify high-risk sites.
The Cowork side panel starts in automatic approval mode. Lower-risk actions can continue without repeated prompts, while sensitive actions such as downloads or entering private information can be paused for approval. Anthropic also names prompt injection as the main risk: hidden instructions inside websites, email or documents may try to steer the agent away from the user's intent.
Anthropic lists content classifiers, action screening, site blocklists, granular permissions and confirmations as safeguards. It also says its current internal configuration reduces known attack success rates below 0.08 percent. That figure should be read as Anthropic's internal test result, not an independent industry benchmark.
The gap is unsigned-in websites
Engadget's framing is useful: Anthropic already has many service integrations, but the browser side panel covers sites without an official connector. For developers it can pair with Claude Code for build-test-verify loops. For office workers it acts more like a temporary web operator inside existing accounts.
The boundaries are still narrow. Claude in Chrome does not support other Chromium browsers or mobile browsers. Tasks involving local files, computer control or Chrome driven from another Claude surface still require the desktop app to be open and connected. Enterprise administrators can also restrict sites with allowlists and blocklists.
What to watch
The first signal is whether Pro rollout turns this from a high-end feature into a default way to work with Claude. The second is whether automatic approval can survive normal workplace use across expense tools, CRM systems, mailboxes, hiring tools and developer consoles.
This is not a model-score story. It is a workflow story: Claude is trying to connect browser state, account context, skills, connectors and history into one continuous work surface.
Sources: Anthropic Claude Help Center, 9to5Mac, Engadget, CocoLoop; checked Cowork side-panel scope, Max/Team/Pro/Enterprise availability, permission list, automatic approval mode, prompt-injection safeguards and browser support limits.