Claude Cowork: cloud tasks for business

Claude Cowork is Anthropic's assistant for multi-step work such as preparing documents and organising files. It can work with connected files and tools without requiring the user to operate a terminal. If someone in your business uses it for recurring reports or document preparation, check how those tasks run before assuming tomorrow's work will behave like yesterday's.

Anthropic's guidance sets 6 October 2026 as the date when new Cowork tasks on Pro and Max run in the cloud and the "Only on your computer" setting disappears. Tasks already started locally stay local. This is the effective date of a previously communicated change, not evidence that Anthropic first announced it today. Read the current Cowork guidance.

The business decision is task-specific. Continue work whose information access and operating arrangements are accepted, change work whose dependencies need attention, and hold work where permission or support remains unresolved. Moving execution to the cloud does not automatically make every task independent of the desktop computer.

Establish which tasks and accounts are affected

Start with the account's plan and current notice. The stated deadline concerns new tasks on Pro and Max. Do not apply it indiscriminately to every Team or Enterprise arrangement. Anthropic also describes a gradual merge of Chat and Cowork naming, so the labels on your account may differ from another person's screen. Check the actual task and account rather than relying on a screenshot of an old selector.

For each business task, distinguish an already-started local task from a new one. A local task that remains open is not evidence that the next task will also run locally. Review recurring schedules too. Anthropic says scheduled tasks move to cloud execution, while tasks that use local files still require the desktop app to be open.

The Cowork getting-started guide explains the practical distinction. Cloud sessions can continue while the desktop app is closed, but access to local files, the browser or the computer depends on the connected desktop being available. A cloud task that needs a spreadsheet on an unavailable computer still has an unmet dependency.

Understand what happens to connected files

According to Anthropic's web, desktop and mobile guidance, connected folders remain on the computer. The task copies needed files into its cloud environment through the open desktop app. Keeping the original folder locally does not mean the task processes no copy elsewhere.

That distinction matters when someone has approved a folder connection under an earlier understanding of the task. Identify which files the work needs, who may authorise their use and what other information sits within the permitted scope. A person being able to connect a folder does not settle whether the business permits that use of its contents.

Check the terms and privacy settings that apply to the actual account. The Pro and Max guidance links training treatment to the "Help improve our AI models" setting. Anthropic's architecture overview addresses Enterprise administrators and describes controls for Team and Enterprise. Do not transfer those plans' commercial training commitments or administrator controls to a Pro or Max account without evidence.

The file guidance also describes deleting task copies with the session under applicable retention practices. That is not a promise that every copy disappears immediately when someone closes a window. If information handling is material to approval, the responsible person must review the applicable terms and obtain clarification before authorising the task. This article does not determine whether a particular use meets your contractual or legal obligations.

Complete an inventory before approving recurring work

Consider a fictional design consultancy using a Pro account to assist with administrative work. The people, documents and test results below are hypothetical. The example does not describe a client engagement or prove that a particular account has the same configuration.

The operations director approves business use. Each task owner accepts the result and keeps the normal business record. A technical administrator checks the account and desktop dependencies. The existing IT supplier helps investigate technical limitations within its agreed scope. Neither the supplier nor the administrator silently takes the director's decision about acceptable information use.

The consultancy completes this inventory rather than approving every task together.

This inventory does not require a new product purchase. It makes the current decision visible. A held task can remain manual, and a useful task can continue within a smaller approved scope.

A local-file test changes the report decision

The scheduled report needs to state which project milestones changed since the previous review. The task owner first defines an acceptance result: the report must use the intended input version, identify the agreed changes and leave uncertain or missing information visible. A fluent summary without the required source is not an accepted report.

The team tests the arrangement separately with fabricated project records and all external actions disabled. The test spreadsheet contains five fictional milestones, with two marked as changed. The planned task needs to read that file through the connected desktop. The administrator makes the test desktop unavailable for the exercise.

The cloud task cannot reach the required local file. The team therefore has no accepted current report. It does not treat any partial output or an older file as a substitute. The operations manager records a failed acceptance result and keeps the controlled manual reporting process in use. The director does not approve the unattended schedule.

The team considers two routes. It could change where an approved input is supplied, subject to verifying the method and information permissions. Alternatively, it could keep the local-file dependency and run the task only when a named person has confirmed the desktop and current input are available. The first route is not assumed to work merely because another cloud service exists.

For this fictional first use, the director chooses the second route. The operations manager changes the proposed process to an attended draft-report task. Before starting it, the task owner identifies the current spreadsheet version and the administrator confirms the desktop connection. The technical supplier helps investigate the setup if the required file remains unavailable. Nobody promises that leaving an app open alone will make every future run succeed.

In the corrected test, the task reads the intended fabricated file and the reviewer checks all five milestones. The output identifies the two changed entries and leaves the other three unchanged. The owner compares the draft with the source before accepting it into the normal reporting process. No message is sent, no live record is changed and no external approval occurs.

The director accepts this attended drafting arrangement. The unattended schedule remains unapproved until its dependencies and failure handling are demonstrated under a separately agreed design. The successful test proves the limited example worked; it does not guarantee future report accuracy or continuous desktop availability.

Record who acts when the next run fails

The task owner needs a clear instruction for a missing input, unavailable desktop or result that does not match the source. In this example, the owner stops using the draft, records the failed check and completes the report through the established manual process. The administrator investigates the connection or task setup. The business approver decides whether the accepted arrangement needs to change.

Keep the checked business record in the system the team already uses for that purpose. Record the input version, task result, reviewer and any corrections needed to explain the decision. A completed AI session is not, by itself, approval to replace a business record or act on its contents.

Agree the supplier's role explicitly. A supplier may help verify technical behaviour without being responsible for the truth of a report, the business's permitted data use or ongoing monitoring. If continuing support is needed, include its scope and handover in the discussion rather than assuming it follows from a software subscription.

Treat an alternative as another transition decision

Anthropic's guidance discusses Claude Code as an alternative for local execution, but says Cowork projects and scheduled tasks do not carry over. Moving to it would require a separate assessment of the people, workflow and technical setup needed. Local execution also does not establish that model inference or every data operation stays on the device.

Choose an alternative because it meets an understood requirement and has passed the relevant checks. Do not switch solely to recover a familiar label or assume that recreating a schedule preserves its behaviour. If the unresolved issue is permission to use the information, changing tools without checking their terms leaves that decision open.

For a wider review of a supplier's evidence and unresolved responsibilities, use the ICT supplier risk management guide. Keep the evidence specific to the service and account you intend to use.

Bring the task decisions to your IT review

Pick one recurring task and record its account plan, required information, execution and desktop dependencies, result owner and current decision. That gives the business approver a concrete choice between continuing, changing the arrangement or holding the work. Revisit it when the task, information access or applicable product terms change.

My IT management consulting can help define ownership, review supplier responsibilities and agree priorities with your existing team. Discuss your recurring AI tasks with the inventory and the decision you cannot yet make. We can agree the advisory scope before work, including where technical implementation or specialist advice needs separate responsibility.