Updated guide · Last verified August 12, 2026
What happens to Claude Cowork when your computer sleeps?
Cowork now spans two different environments: cloud or remote sessions for work that can continue away from your laptop, and the Claude Desktop app when a task needs your local files or local computer. The important change is not that every task runs “while you sleep”; it is knowing which environment the task requires before you depend on it.
Does Claude Cowork keep working if your computer sleeps?
It depends on where the task is running. If the task needs local files, the Claude Desktop app, or control of your local computer, putting that computer to sleep can pause or interrupt the work. If the task runs in a supported cloud or remote session and its required connectors remain available, it can continue without the laptop staying awake.
Local folder or desktop task
Keep the computer awake, connected, and signed in until the task finishes.
Cloud or remote session
The work may continue after the laptop closes when it does not depend on local resources.
Unsure which environment applies
Ask where the task will run and test a short, reversible job before relying on unattended execution.
For setup and current platform guidance, use the Claude Cowork login, download, and setup guide.
Local computer work versus remote sessions
Use the Desktop app when your task needs local files, a local folder, or interaction with your computer. Remote or cloud sessions can continue after your laptop is closed when the work does not depend on that local environment. Before you schedule or hand off important work, identify the data source, required connector, and where the resulting file should be delivered.
Do not treat computer use as an unattended permission grant. Start with a narrow task, read the proposed plan, and review any action that can change files, send a message, or modify a connected service.
Make recurring tasks specific and reviewable
Recurring tasks are most useful when the prompt names the source, time window, output format, destination, and exception rule. That gives you a reliable artifact to inspect rather than an open-ended automation.
A weak prompt
Summarize my emails from the past week.A stronger prompt
Every Friday, review emails received in the last 7 days. Exclude newsletters. List sender, subject, one-sentence summary, and required action. Draft the result as markdown. Do not send, delete, move, or modify anything without asking me first.For the first run, inspect the output and tighten the prompt. Recheck recurring tasks after a model, connector, or permission change.
Safety checklist before you automate
- Use a dedicated folder or a narrowly scoped connector—not your entire drive or workspace.
- Ask Cowork to produce a plan and a draft before permitting write actions.
- Put irreversible actions, external messages, payments, and deletions behind explicit approval.
- Review the first few runs and revoke access when the task no longer needs it.
Current product guidance
Claude’s product behavior evolves quickly. Check the official guidance before relying on a particular device, plan, or scheduling behavior:
The practical rule: choose the environment deliberately, keep the scope narrow, and treat automation as a workflow you verify—not a black box.
Until next time.
— The ClaudeCowork.com team