top of page

Claude computer use reaches Team and Enterprise in beta, off by default

3 hours ago
8 min read

Updated: 15 minutes ago

Cover image with the Claude logo and the title Claude computer use reaches Team and Enterprise in beta, off by default. Data Studios original cover

Anthropic has opened Claude computer use to business customers. In a release notes entry dated November 20, 2026, the company said that computer use, the capability that lets Claude see a user's screen and work inside the desktop apps that user allows, is now in beta on the Team and Enterprise plans. Until this week the feature was limited to the individual Pro, Max and Ultra plans, and Anthropic's own help pages stated plainly that Team and Enterprise organizations did not have access.


The business version arrives with a set of controls that the consumer version does not need. Computer use is off by default for every Team and Enterprise organization, and only an Owner or Primary Owner can switch it on. It runs only inside the new unified Claude experience, where chat and Cowork are merged, and it is being rolled out to organizations gradually, so some administrators will not see the toggle yet. Enterprise customers can restrict it by role, both plans can limit which applications Claude may touch with allow and block lists, and IT teams can keep it disabled on specific machines through a device management policy.


The feature works in Claude Desktop on macOS 14 or later and on Windows. Users can also start computer use from Claude on the web and from the Claude mobile apps, provided the organization's separate "Computer access" setting is on and a computer running Claude Desktop is open and connected. Several regulated configurations are excluded outright: organizations with a HIPAA-ready setup, Zero Data Retention for Claude Code, customer-managed encryption keys or FERPA and K-12 settings cannot enable it.


··········


⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣

HOW CLAUDE COMPUTER USE WORKS ON THE DESKTOP.


Computer use is the slowest and most general of the three ways Claude can act on a user's behalf. Anthropic's documentation describes an order of preference. Claude first tries a connector, such as Gmail, Google Drive, Microsoft 365 or Slack, because a direct integration is faster and more reliable. If no connector fits, it uses a browser, either the browser built into Claude Desktop or the user's own Chrome through Claude in Chrome. Only when neither works does it fall back to operating the screen directly, clicking, typing and opening applications the way a person would.


To do that, Claude takes screenshots of the screen and decides on its next action from what it sees. Anthropic gives examples such as compiling a competitive analysis from local files into a formatted report, testing an app inside a phone simulator, or working in internal dashboards that have no connector. On macOS 15 and later, Claude works in background windows by default, does not take over the pointer or keyboard and generally waits while the user is typing. The first time a task needs the full screen in a session, it asks for permission, and users can grant full control in settings.


Every application requires explicit approval. Claude asks before it interacts with each app for the first time, and some categories, including investment, trading and cryptocurrency platforms, are off limits by default. The company also says Claude is trained to avoid risky actions such as transferring funds, deleting files or entering sensitive data, and to flag signs of prompt injection, while acknowledging that these safeguards are imperfect. The computer must stay awake with Claude Desktop open for a task to continue.


··········


CLAUDE COMPUTER USE AVAILABILITY BY PLAN.


The business rollout differs from the individual plans in who decides, where the feature runs and what is excluded. The table below sets the two side by side, with Google's newly launched computer use for the Gemini Mac app as a reference point, using only what each company has documented.


........


Item

Claude Pro, Max, Ultra

Claude Team, Enterprise

Gemini app for Mac

Status

Available

Beta, gradual rollout

Rolling out from Nov 19, 2026

Default

User turns it on

Off until an Owner enables it

User downloads the Mac app

Who enables it

The user

Owner or Primary Owner

The user

Platforms

Claude Desktop, macOS and Windows

Claude Desktop, macOS 14+ and Windows

Mac app only

Web and mobile

Through Claude Desktop

Only with "Computer access" on

Not documented

Account types

Personal plans

Organization accounts

Personal accounts, 18+, U.S., English

Per-app approval

Yes

Yes, plus admin allow and block lists

User chooses apps


........


The comparison with Gemini shows how the two companies are pitching the capability. Google's version, announced on November 19, targets subscribers to Google AI Plus, Pro and Ultra on personal accounts in the United States. Anthropic has gone the other way this week, extending an existing consumer feature into managed workplaces where an administrator, rather than the individual, decides whether Claude may operate desktop software at all. Readers comparing the two products can find more detail in our coverage of Gemini computer use in the Mac app.


··········


WHAT CHANGES FOR CLAUDE TEAM AND ENTERPRISE ADMINS.


Turning the feature on takes two steps in Organization settings under Capabilities. The Owner first enables "Chat and Cowork unified" and then the Computer use toggle listed under Claude Desktop. Computer use does not work in separate Cowork tasks or in Claude Code, so organizations still on the older split between chat and Cowork will not see it in practice. For Team organizations, Anthropic's documentation says the unified experience turns on by default on December 1, 2026 unless an Owner selects "Keep disabled" beforehand, and the separate chat and Cowork experience is retired on February 1, 2027. Computer use itself remains off until it is enabled separately.


Switching the feature off is not instantaneous. Anthropic says the change can take about an hour, and sometimes longer, to reach each user, which admins should plan around if they need to stop it quickly. Our guide to Claude Enterprise security configurations and deployment controls covers the wider set of settings that sit alongside this one, and our report on the Claude Enterprise security center and EDR sensors describes the monitoring tools introduced earlier this month.


Role controls are where the two business plans part ways. On Enterprise, the built-in User, Admin, Owner and Primary Owner roles receive computer use as soon as it is enabled. To exclude someone, an admin moves that person to a custom role and waits about 15 minutes, and custom roles set to "All capabilities" must first be changed to "Only selected" before computer use can be removed from them. Team plans have no custom roles, so the organization-wide setting applies to every member. Companies weighing the two tiers on governance can compare them in our ChatGPT Business vs Claude Team comparison.


··········


[[ADPLUS_300x250_1]]

CLAUDE COMPUTER USE APP ALLOW AND BLOCK LISTS.


Administrators can choose between two list modes. "Block these apps" denies the listed applications and permits the rest, while "Allow only these apps" denies everything that is not on the list. In both modes users still approve each permitted app themselves, so the admin list sets the outer boundary and the individual approval remains in place inside it. Users running an outdated version of Claude Desktop lose computer use entirely while an allow list is active, until they update.


Applications are identified differently on each operating system. On macOS the list uses bundle identifiers, with Anthropic giving com.microsoft.Excel as an example, while on Windows it uses the program file name or an application user model ID. Anthropic warns that typed identifiers are not validated, so a misspelled ID silently fails to match. On Windows, some programs display windows owned by a different executable, and the company cites LibreOffice, whose windows belong to soffice.bin, as a case where the window's file name may also need blocking.


Anthropic is explicit about what the lists do not cover, and the exclusions are substantial. They do not apply to Claude in Chrome, the built-in browser, Claude Code or desktop extensions, nor to websites and browser extensions, apps running inside remote desktops or virtual machines, text copied out of a denied app, recordings made with the Record a skill feature, or Windows notifications, the Start menu, search and File Explorer. They also cannot stop indirect effects, where an approved app causes something to happen in a denied one. Anthropic's own example is a link clicked in an email that opens Chrome even though Chrome was never approved.


··········


DEVICE MANAGEMENT POLICY FOR CLAUDE COMPUTER USE.


For organizations that manage their fleet centrally, Anthropic has added a policy key named computerUseEnabled. Setting it to false keeps computer use off on the chosen computers, and it requires Claude Desktop version 5.1231.0 or later. The key is deployed at the machine level rather than per user: on macOS as a Boolean in a configuration profile for the com.anthropic.claudefordesktop domain, and on Windows as a DWORD value of 0 under HKLM\SOFTWARE\Policies\Claude. The change applies once Claude Desktop has been fully quit and reopened, and Anthropic notes that older Windows versions of the app may reject the whole policy if this key is the only value present, so the app should be updated first.


The company describes the key as a way to keep the feature off, and stresses that it is not a security lock. It does not cover Record a skill, Claude in Chrome, the built-in browser, Claude Code in a terminal, local MCP servers or desktop extensions. Device management also cannot do the reverse: it cannot turn computer use on, approve apps for users or enable macOS Screen Recording by itself. On the user side, each person must install the latest Claude Desktop and turn on "Enable computer use" for each computer and account, and on macOS grant Accessibility and Screen Recording permissions. On macOS 27 the Accessibility permission appears under the label "Device Control and Data Access".


··········


CLAUDE COMPUTER USE PRIVACY AND DATA HANDLING RISKS.


The documentation for both the individual and business versions states that computer use has no sandbox between Claude and the user's applications. Anything visible on screen can influence what Claude does next, which is the route prompt injection would take, and computer use is not confined to the folders a user has connected, so folder limits and "Read only" settings do not apply to it. For security teams, this is the most consequential sentence in the release, because it means the protection rests on app approvals, admin lists and Anthropic's automated review rather than on isolation.


Screenshots taken during a task are saved with the chat and may contain personal or confidential information. Anthropic also runs an automated action-review check that can see the latest screenshot, and the company says it may keep a copy as part of its record of that check. For Team and Enterprise customers, this data is governed by the Commercial Terms and the Data Processing Addendum. Anthropic's guidance for individual users recommends closing sensitive files before starting and avoiding banking, healthcare and government applications, advice that maps directly onto the block lists business admins can now configure.


··········


⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁤

CLAUDE COMPUTER USE FOR BUSINESS: CONFIRMED FACTS AND OPEN QUESTIONS.


The documented facts are clear. Computer use is in beta on Team and Enterprise from November 20, 2026, it is off by default, only an Owner can enable it, it depends on the unified chat and Cowork experience, and it ships with role controls on Enterprise, app allow and block lists on both plans and a machine-level policy key for managed devices. Regulated configurations such as HIPAA-ready, Zero Data Retention for Claude Code, customer-managed keys and FERPA or K-12 settings are excluded.


Anthropic has not published a date for general availability, nor said how computer use activity counts against seat allowances beyond the general rule that usage beyond a member's allowance in the unified experience is billed at standard rates when usage credits are on. The setup documentation also does not describe audit logging specific to computer use actions. With no sandbox and with app lists that do not reach browsers, remote desktops or indirect effects, the practical decision for most IT teams will be whether to start with a narrow allow list for a pilot group, which Enterprise roles make possible and Team plans, lacking custom roles, do not.


··········


FOLLOW US FOR MORE.


·····


DATA STUDIOS


·····


datastudios.org


bottom of page