Claude Cowork is Anthropic's way to give Claude a multi-step knowledge-work task instead of asking for a chat answer alone. It can work with files and connected tools to produce documents, analyze data, and carry out browser tasks. You do not need a terminal to use it.

Cowork is also becoming part of the regular Claude experience. The rollout means one account may still have separate Chat and Cowork options while another starts work from a single message box.

At a glance

  • Cowork requires a paid Claude plan. Availability and organization controls differ by platform.
  • Cloud work can continue after you close your laptop. Tasks that need your local files or built-in browser still need an online desktop connection.
  • The built-in browser is separate from your personal browser. Claude in Chrome is a different route that uses your Chrome environment.
  • Granted access lets Claude take real actions. Review the plan and output, especially for work with consequences.

What Cowork is for

Anthropic describes Cowork as the knowledge-work counterpart to Claude Code, using the same agentic approach without requiring a terminal. Its documented tasks include turning notes into reports, analyzing files, making spreadsheets with formulas, and creating presentations.

You describe an outcome and Claude works through the steps. It can split work into subtasks and show progress while you steer it. A plugin can bundle skills, connectors, and sub-agents for a particular role or workflow.

These are documented capabilities, not a guarantee that a generated spreadsheet or report is correct. Check calculations and citations before using the result. This guide is based on official documentation, not our own hands-on tests.

Plans, platforms and the rollout

The getting-started guide lists Pro, Max, Ultra, Team and Enterprise. It does not list Free access.

  • Claude Desktop is listed for macOS, Windows and Linux beta on all paid plans.
  • Web and Claude Mobile are listed for Pro, Max, Ultra and Team, with Team in beta. Enterprise access requires an owner to enable it.
  • The unified Chat and Cowork experience is rolling out to Pro, Max and Ultra. Team and Enterprise organizations have a separate "Chat and Cowork unified" setting, with Team in beta.

Do not use the presence or absence of a Cowork button as the only availability check. In the unified experience, Claude can bring in Cowork capabilities when a task needs them. Until that experience reaches an account or organization, Cowork remains next to Chat.

What the Linux beta label does not establish

The availability list includes Linux beta, and the dedicated browser guide explicitly supports the built-in browser there. However, the general guide's requirements for local file access, browser use and computer use still name macOS or Windows.

Those statements do not establish that every local-file or computer-use capability has Linux parity. For Linux, rely on the specific capability documentation rather than extending the general availability label to all desktop features.

Cloud work versus access to your computer

A cloud session can keep working while your laptop is closed. Anthropic says Cowork runs tasks on its servers and saves sessions and files to your Claude account. You can start work on one platform and check the same session from another.

Access to something on your own computer is different. Local files, the built-in browser and computer-use tasks need the desktop connection described in the help guide. Keep the required desktop app open and connected for that part of the task.

For example, cloud work on files already available to the session is not the same as reaching a folder on a sleeping laptop. Closing the laptop does not make its local resources available in the cloud.

How the built-in browser differs from Claude in Chrome

The browser guide describes two ways Cowork can work with websites.

The built-in browser opens beside the task in Claude Desktop. It is separate from your personal tabs and saved logins. Sites you deliberately sign in to there can remain available to future Cowork sessions on that computer, so separation does not mean those sessions never retain account access.

Claude in Chrome uses the extension in your own Chrome browser and the accounts available there. If you already use Claude in Chrome, it stays the default for Cowork web tasks. Otherwise, the built-in browser is the default. These are different access paths, not two names for the same browser.

The desktop app still matters

The built-in browser lives in Claude Desktop and needs the app open and online, even though the Cowork session runs in the cloud. A task on web or mobile can use that browser while the desktop app stays connected. This is not a browser that runs independently on your phone.

The browser guide lists macOS, Windows and Linux beta on Pro, Max and Ultra, plus Team and Enterprise unless an organization owner has disabled it. Enterprise cloud access and the organization's browser controls are separate settings. Enabling one does not establish the other.

Browser permissions and risk

Anthropic says Claude asks permission before acting on a site for the first time, blocks high-risk sites, and checks each action against the requested task. It also says these protections cannot remove prompt-injection risk.

The browser guide strongly advises against using either browser route for actions involving sensitive financial accounts, medical information or other people's personal data. Treat a website's instructions as something to review, not as a reason to grant the agent more access.

File access, approval modes and network limits

Cowork can read and write the local folders you grant it access to. The help guide says permanent file deletion requires explicit permission. Server-side isolation does not undo the file or connector access you have granted.

In the unified experience, Auto is the default on Pro, Max, Ultra and Team, while Manual is the default on Enterprise. Manual asks for permission for actions that need it. Auto reviews actions without pausing at every step and can block them. Neither setting is a promise that every action is safe.

Organization settings and connector permissions still apply. Administrators can control whether automatic approval is available, and an organization may require per-task approval for tools that can write. Do not assume a personal approval preference overrides those rules.

There is also a network qualification worth reading. Although the help guide describes network egress settings, it explicitly says those settings do not apply to web fetch, web search or MCPs, including Claude in Chrome. Web fetch runs server-side and is limited to search results and URLs you have shared. Do not treat the general egress description as a guarantee covering all tools.

A sensible first task

Start with a non-sensitive copy of a document or dataset and ask for a specific deliverable. For example, ask Claude to summarize supplied notes into a report, retain source references, and flag missing information rather than fill it in.

Before it starts, review which files and tools the plan needs. Afterward, compare the output with the inputs. A task that only needs supplied notes does not need access to unrelated folders or websites.

Multi-step work uses more capacity than a quick chat question because each step consumes tokens. The help guide also says sessions cannot be shared, although individual artifacts can be. Do not plan around unlimited usage or shared sessions.

FAQ

Is Claude Cowork free?

No. The current getting-started guide lists paid Pro, Max, Ultra, Team and Enterprise plans. Platform rollout and organization settings still affect access.

Do I need Claude Desktop for every task?

No. Cowork has web and mobile access for supported plans. However, access to resources on your computer needs the relevant desktop connection. The built-in browser specifically needs Claude Desktop open and online.

Can it keep browsing after I close my laptop?

Do not infer that from cloud-session continuity. The built-in browser needs the desktop app online. A cloud session continuing is different from a task retaining access to a disconnected local browser.

Can it automatically see my personal browser accounts?

The built-in browser is separate from your personal browser and does not automatically inherit its logins. Accounts you deliberately make available there can persist across sessions. Claude in Chrome is a separate route using your own Chrome environment.

Why do some accounts no longer show a Cowork tab?

The unified Claude experience is rolling out. In that version, a conversation can take on a Cowork task without a separate Chat or Cowork choice. Organization controls and rollout status still matter.

Sources