Claude in Chrome vs computer use: which one Claude uses, and when the extension is not enough
Claude in Chrome works on web pages in your Chrome; computer use works in desktop apps and only looks at browsers. What each one does, Cowork's built-in browser, and what to use beyond both.
Short answer: Claude in Chrome is for web pages: it reads, clicks, types and fills forms in your own Chrome, with the accounts you are signed in to. Computer use is for desktop apps without a better tool: Claude operates them through screenshots, but it can only look at browsers, never click or type in them. Claude picks for you in a fixed order (connector, shell, browser, then the screen), so the two do not compete. When a task needs another browser, other agents, several sessions at once or a plan without computer use, connect a computer use MCP server instead.
The two tools at a glance
As documented by Anthropic in October 2026:
| Claude in Chrome | Claude's computer use | |
|---|---|---|
| What it operates | Web pages in Chrome (Claude Code: also Edge and other Chromium browsers) | Desktop apps on your screen |
| Browsers | Full control: read, click, type, navigate, fill forms | View only, in screenshots |
| How it sees a page | The page itself, plus console, network requests and DOM state | Screenshots of the screen |
| Your logins | Shares your Chrome login state | Not applicable in browsers |
| Where you start it | Chrome side panel, Claude Desktop (Chat, Cowork, Claude Code), Claude Code CLI and VS Code extension | Claude Desktop (macOS, Windows), Claude Code CLI (macOS only) |
| Plans | Pro, Max, Team, Enterprise | Pro and Max only |
| With API keys or cloud providers | No, Claude Code needs a claude.ai login | No |
Sources: Get started with Claude in Chrome, Use Claude Code with Chrome, computer use in the CLI, Claude Desktop docs.
How Claude decides which one to use
You rarely choose yourself. Anthropic documents a fixed order: a connector or MCP server for the service if you have one, the shell for commands, the browser for web work (Claude in Chrome, or in Cowork the built-in browser), and computer use for everything else.
The control tiers enforce that order. In computer use, browsers and trading platforms are view only, terminals and IDEs click only, everything else gets full control, and Anthropic says screen control is "reserved for things nothing else can reach, like native apps, hardware control panels, or proprietary tools without an API." So computer use will never fill out a web form for you: without a browser tool, Claude can only look at the page in a screenshot.
What Claude in Chrome does well
Claude in Chrome is a browser extension, and Claude acts on the page directly. Anthropic names signed-in web apps such as Gmail, Google Docs and Notion without an API connector; web development, where Claude Code builds a site, reads console errors, network requests and DOM state in Chrome and fixes the code; form filling from local files; data extraction; and file uploads of up to 10 MB. Saved shortcuts can run on a schedule, and the classic side panel can record a workflow you show it once.
In Claude Code, Claude opens its own tabs and works "in a visible Chrome window in real time". On a login page or a CAPTCHA it stops and asks you. Anthropic blocks some high-risk sites and asks before Claude opens financial sites.
For web tasks in Chrome, it is the better tool: it works on the page instead of on pixels, so it is faster and more exact than any screen-based approach.
Claude in Chrome vs Cowork
Less of a choice than it sounds: Cowork is the agent mode in Claude Desktop, and for web tasks it uses one of two browsers, set under Settings > Cowork > Preferred browser:
- Claude in Chrome: your own Chrome, on the page in front of you, with your accounts.
- The built-in browser: a browser inside Claude Desktop (macOS, Windows, Linux beta), with "the same browsing capabilities as Claude in Chrome". It is separate from your browser and does not touch your tabs. You can import logins site by site from Chrome, Edge or Firefox on macOS, and from Firefox on Windows and Linux. Import from Safari is not available. It is rolling out gradually as of late October 2026.
If you already use Claude in Chrome, it stays the default; otherwise Cowork uses the built-in browser (source). For desktop apps, Cowork falls back to computer use on Pro and Max. The Chrome side panel itself is turning into a Cowork session, starting with Max and Team, so its conversations appear in your Cowork history.
When the extension is not enough
Claude in Chrome stops at the edge of Chrome, and Claude's computer use deliberately does not take over browsers. That leaves gaps:
- You work in Safari or Firefox. Claude in Chrome is not available there, and the built-in browser cannot import Safari logins. For Safari, this guide covers the options, including Apple's Safari MCP server.
- The task spans the web and Mac apps. Download the invoice, then enter it in Numbers. On Pro or Max, Cowork can use the browser for the download and computer use for Numbers. On Team or Enterprise, computer use is not available at all.
- You use Claude Code with an API key or a cloud provider. Anthropic keeps Chrome integration off for API keys and long-lived tokens, and neither it nor computer use works through Amazon Bedrock, Google Cloud or Microsoft Foundry.
- Other agents need the browser too. Claude in Chrome connects to Claude's own apps: the side panel, Claude Desktop and Claude Code. Codex, Cursor or GitHub Copilot in VS Code have no documented way to use it.
- Several sessions need the screen. In the Claude Code CLI, only one session at a time can use computer use; it holds a lock until it exits.
Computer use for any browser with ShadowCursor
ShadowCursor is a Mac app and MCP server that gives Claude Code, Claude Desktop, Codex, Cursor, VS Code and any other MCP client their own cursor, keyboard, clipboard and windows. Each agent's cursor is drawn in its color with a name tag. It is not bound to the built-in tiers: browsers are apps like any other, so an agent opens a window of its own in Safari or Chrome and clicks, types and fills forms there, also while your windows cover it.
- Any browser and any app in one task. The same agent reads a PDF in Preview, enters the data on a web page in Safari, and saves a confirmation in Numbers.
- Any MCP client, any Claude plan. It runs as a normal MCP server, so it also works on Team and Enterprise and with API keys.
- Several agents at once. Each in its own browser window, with its own cursor and clipboard.
- Human input. The pointer moves in curved paths with natural speed, and typing has a human rhythm at about 200 words per minute, so sliders, date pickers and signature fields respond as they do to a person. Hover menus react in Safari; in Chrome, hover without a click does not reach the page.
To set it up, open the app, allow Accessibility and Screen Recording, and connect Claude with one click; the app finds Claude Code and Claude Desktop and adds itself. Claude in Chrome and ShadowCursor can be connected at the same time; name the tool in your request when you want a particular one.
Its limits: an agent cannot use a background tab of your browser window, so it opens its own window. It works through screenshots and the accessibility interface, not the page's code, so it cannot read the console or network requests the way Claude in Chrome does. Minimized windows cannot be seen or operated, and dragging files, tabs or text between windows is cancelled rather than dropped. After a 7-day free trial without a card it costs $12.99 per month or $69.99 per year. For how background operation works in general, see background computer use on the Mac.
Which one to use
- Web task in Chrome: Claude in Chrome.
- Web task you want to hand off without touching your browser: Cowork's built-in browser.
- Native app, one task at a time, Pro or Max: Claude's computer use; setup on the Mac.
- Scripted browser tests: Playwright; see Playwright MCP vs computer use.
- Safari, other agents, several at once, Team, Enterprise, API keys, or web plus Mac apps: a computer use MCP server such as ShadowCursor.
FAQ
Is Claude in Chrome the same as computer use?
No. Claude in Chrome is a browser extension that works on web pages in Chrome. Computer use operates desktop apps through screenshots, pointer and keyboard, and in browsers it can only look.
Can Claude's computer use fill out web forms?
Not in a browser. Anthropic caps browsers at view only, so Claude can see the form in a screenshot but cannot type into it. Use Claude in Chrome, Cowork's built-in browser, or a computer use MCP server that is not bound to that tier.
Do I need Claude in Chrome if I use Cowork?
Not necessarily. Cowork has a built-in browser in Claude Desktop with the same browsing capabilities. Claude in Chrome is the better choice when the work is on a page you already have open, in the accounts you are signed in to in Chrome.
Does Claude in Chrome work on Team and Enterprise plans?
Yes, on Pro, Max, Team and Enterprise; on Team and Enterprise the organization's owner controls whether it is available. Claude's computer use, by contrast, is Pro and Max only.
Can I use Claude in Chrome and ShadowCursor together?
Yes. Claude in Chrome connects through the extension and ShadowCursor as an MCP server, so one Claude session can have both: the extension for pages in Chrome, ShadowCursor for other browsers and Mac apps.