Claude Computer Use for Team and Enterprise: Admin Guide
Claude computer use is now in beta on Team and Enterprise plans. Where it works, how admins turn it on, limit apps and roles, and the security caveats to know.
PromptWises is reader-supported. Some links may earn us a commission at no extra cost to you. This never affects our ratings or recommendations.
Claude can now work on your employees’ desktops. On November 20, 2026, Anthropic made computer use available in beta on Claude Team and Enterprise plans: Claude sees a user’s screen and clicks and types in the desktop apps they allow. It is off by default and rolling out to organizations gradually, so nothing changes until an Owner switches it on. Everything below comes from Anthropic’s release notes and its admin setup article, both read on 21 November 2026.
Where Claude computer use works
Computer use only runs in the new unified Claude experience, which needs the Chat and Cowork unified capability turned on. We covered that change in Claude Enterprise merges chat and Cowork. Inside it, users can start computer use from:
| Surface | Requirement |
|---|---|
| Claude Desktop | macOS 14 or later, or Windows |
| Claude on the web, Claude Mobile | Organization’s Computer access setting on, and a computer with Claude Desktop open connected to the chat |
It does not work in tasks started with the separate “Cowork” option, or in Claude Code. Each user also has to turn on Enable computer use in the latest Claude Desktop, per computer and per account. On a Mac, it needs the Accessibility and Screen Recording permissions; Windows needs no extra OS permission.
Some organizations cannot turn it on at all: those with the HIPAA-ready configuration, Zero Data Retention for Claude Code, customer-managed encryption keys (CMEK), or FERPA/K-12 settings.
What admins control
Only an Owner or Primary Owner can switch it on, under Organization settings > Capabilities > Claude Desktop > Computer use. If the toggle is missing, the beta has not reached the organization yet. The controls:
- Roles (Enterprise only). Computer use is a capability in custom roles. Users with a built-in role (User, Admin, Owner, Primary Owner) get it as soon as it is on, so move anyone who should not have it to a custom role and wait 15 minutes first. Team plans have no custom roles, so the setting covers every user.
- App access. Choose a block list (for example, a password manager) or an allow-only list where every other app is denied. Users still approve each app themselves.
- MDM. Setting Claude Desktop’s
computerUseEnabledpolicy key tofalsekeeps computer use off on chosen computers, whichever account signs in. It needs Claude Desktop 5.1231.0 or later.
Plan for lag. Turning computer use off, removing a role or changing an app list can take about an hour, sometimes longer, to reach each user’s Claude Desktop. Until then the old setting still applies.
The security caveats Anthropic spells out
This is the part IT teams should read twice:
- No sandbox. There is nothing between Claude and the apps a user approves. Content on screen, such as a web page or an email, could cause Claude to take unintended actions.
- Folder limits do not apply. Through approved apps, Claude can open, change or delete files outside the folders a user has connected, and “Read only” folders are not protected.
- Screenshots are stored. Claude takes screenshots to navigate, they are saved with the chat, and the automated check that reviews Claude’s actions can see the latest one.
- The app lists have gaps. They do not cover Claude in Chrome, Claude Code, browser extensions and websites, apps inside a remote desktop or virtual machine, or text copied out of a denied app.
An allow-only list of the few apps a team needs is the safer start.
How it compares with Gemini on the Mac
A day earlier, Google added computer use to the Gemini app for Mac. The two launches target different buyers. Gemini’s is for personal Google accounts on AI Plus, Pro or Ultra, in English in the U.S., on Apple Silicon Macs, and runs in an isolated background window. Claude’s is for business plans, covers both macOS and Windows, and comes with organization-level controls instead of a consumer rollout. Neither vendor has published usage limits for the feature.
Should your organization turn it on?
Anthropic mentions no separate price for the beta, so the question is risk, not cost. If your team already uses the unified Claude experience and has repetitive desktop work, pilot it with a small Enterprise custom role and a short allow list, and test on non-sensitive data first. If you are on a regulated configuration, the decision is made for you. For plan prices see our Claude pricing guide, and for how Claude performs overall read the Claude review. More launches are tracked in our news section.
Frequently asked questions
Is Claude computer use available on Team and Enterprise plans?
Yes, in beta since November 20, 2026. It is off by default and rolling out to organizations gradually, so an Owner or Primary Owner has to turn it on under Organization settings > Capabilities once it reaches the organization.
Does Claude computer use work in Claude Code or Cowork?
Not on Team and Enterprise. Anthropic's setup article says it works only in the new unified Claude experience, and not in tasks started with the separate Cowork option or in Claude Code.
Which operating systems does Claude computer use support?
Claude Desktop on macOS 14 or later and on Windows. Users can also start it from Claude on the web or Claude Mobile if the organization's Computer access setting is on and a computer with Claude Desktop open is connected to the chat.
Can admins stop Claude from using certain apps?
Yes. The App access setting has a block list and an allow-only list, and on Enterprise plans computer use can be limited by custom role. Anthropic notes the lists do not cover browser extensions, websites, Claude in Chrome or apps inside remote desktops.
Is Claude computer use safe for confidential data?
Anthropic's own article warns that there is no sandbox between Claude and approved apps, that folder limits and Read only settings do not apply, and that screenshots are saved with the chat. Treat it as access to the user's whole desktop and limit apps accordingly.