Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- October 6 is a future effective date. This article checked official guidance on October 4 and does not describe the change as already fully completed.
- A task continuing in the cloud does not mean it can still read local files after you turn off your computer.
- For work that must execute locally, consider Claude Code. Check the exported content and working directory before continuing.
Who is affected and what changes in settings
Anthropic's Cowork getting-started guidance specifically names Pro and Max: from October 6, 2026, new tasks execute in the cloud, the Only on your computer option under Settings > General is removed, and users do not need to configure anything separately. This article's verification date is October 4. The official notice provides neither an exact transition time zone nor its original announcement date.
First confirm whether you use a personal Pro/Max account or a company Team/Enterprise workspace. Do not apply this personal-plan notice directly to organizational accounts, or delete and recreate an existing running task just because an option disappears. Record the task name, where it was created, and its current progress to help assess subsequent behavior.
Existing tasks remain, and local folders are not moved wholesale
Existing local tasks can continue to completion. Original folders remain in place; the cloud obtains copies of connected files only as needed, without moving the whole folder.
For an ordinary cloud session to access local files from the web or a phone, the session must still have started on desktop, Claude Desktop must remain open on the original computer, and the files must be in a connected directory. A cloud session continuing to run and local files being accessible are separate conditions.
Try a read-only sample before handing over real work
Put a text file containing no customer information in a dedicated test directory, with an easy-to-check marker and two or three facts. After the transition, or once your account can create cloud tasks, authorize only that directory, start a cloud task from desktop, and ask it to return the marker and a summary without changing or sending files. Accounts that still use only local mode before the transition can prepare the sample first. This is preparation advice, not a test report of the future transition.
Keep the desktop app open and open the original session on the web or a phone using the same account. Check that the result references the correct file. If you need to generate files, use a separate copy to verify the output location and actually open the result to inspect its content. After the test passes, replace the real inputs one at a time. Avoid changing the device, directory, and task prompt together, which would make failures harder to isolate.
If the Cowork button is missing, identify the interface change first
Claude is also gradually merging Chat and Cowork. Official guidance for the unified experience says Pro/Max users who no longer see two mode choices can describe their task directly. Accounts on the same plan may receive the new interface at different times. Do not confuse this phased interface change with the October 6 execution-location notice.
If you still have a mode selector, use the current interface. In the new interface, check folder permissions in Trusted folders and the output directory in Storage folder. If results are missing, check files in the original session before their save location. Do not resubmit an entire task just because the home-page layout changed.
When local files are inaccessible, check each dependency
First check the network and whether the desktop app is open on the original computer, then verify where the session started, connected directories, and file permissions. Getting-started guidance requires an ongoing internet connection; local execution does not mean the model works offline. If an old local task stops, also check whether the computer went to sleep or the app closed.
When troubleshooting, describe the missing file and expected result in the original session. Check whether content has already been generated or changed before deciding to retry. Keep redacted error text, the time of occurrence, client version, and test filename. If the sample also fails, giving these details to official support is more useful for finding the cause than repeatedly broadening folder permissions.
How to continue in Claude Code when execution must stay local
The official continuation path is to download the transcript from the banner at the top of an existing task, or download Cowork history from the in-app notification, then open it in Claude Code. Projects and scheduled tasks do not migrate with this record.
Treat the exported record as handoff material. First check that key decisions, unfinished work, and file references are complete, then select the correct local working directory. Ask Claude Code to restate what it will do next and allow writes only after human confirmation. Importing chat history does not automatically restore the original task's execution state, all its files, or its permissions.
Check scheduled tasks and privacy settings separately
As of this article's verification, cross-device help and scheduled-task help were not fully consistent in describing local-file binding and execution location. For scheduled work that depends on local files, first check its configuration, most recent result, and next run time in Scheduled, then run it on demand with nonsensitive input. This does not establish that all tasks have migrated or that local files remain accessible after shutdown.
Execution location and data use also need separate consideration. Commercial data commitments in architecture documentation cannot be applied directly to personal Pro/Max accounts. Personal accounts should check Help improve our AI models under Settings > Privacy. For work with strict restrictions on where information is processed, confirm organizational requirements and the product's actual path before assigning it to a cloud task.
Sources
Frequently Asked Questions
Will existing local tasks be deleted after October 6?
Official guidance says existing local tasks remain and can continue to completion. Record their original location and progress first; there is no need to delete old sessions because of the new-task rule.
Can I turn off my computer because Cowork runs in the cloud?
Assess cloud-only work separately from access to local resources. If a task needs local files, apps, or other resources, desktop access requirements still apply.
Is migration complete once I import the history into Claude Code?
Not yet. Recheck files, the working directory, unfinished work, and permissions, then ask it to restate the next action.
Is this a shared transition date for Team or Enterprise?
The October 6 notice discussed here explicitly targets Pro/Max. Organizational accounts should follow their own administrative configuration and official notices.