Claude Cowork Just Changed How AI Works While You’re Away From Your Computer
Close the Laptop, Walk Away, Come Back to a Finished Task. Here’s What That Actually Means for How You Delegate.
It is 6 PM, and a task is sitting on your plate that will take Claude a while: going through a week of emails, pulling the key points, and writing a clean summary. In the old way of working, you would start it, then watch your screen, afraid to close the lid because the whole thing might stop.
That small fear shaped how people used AI agents for months. The task lived on your computer, so the task needed your computer. Sleep, shut down, or lose Wi-Fi, and the work stopped with it.
That has changed. Claude Cowork now runs in the cloud, which means Claude’s work happens on Anthropic’s servers instead of your machine. You can hand something off, close the laptop, and come back to the result later.
Before diving in, one quick thing. Tools like Cowork are moving fast, and getting real value from them takes more than clicking around until something works. If learning to use Claude well is worth your time, that is exactly what The Ultimate Claude Toolkit is there for.
👉 [Get The Ultimate Claude Toolkit]
Now let’s talk about what this shift actually means for the way you work.
1. Tasks Keep Going After You Close the Lid
Here is the plain version. When Cowork runs in the cloud, Claude works in an isolated environment on Anthropic’s servers, and your sessions and files are saved to your Claude account. Close your laptop and Claude keeps going.
This matters most for tasks that take a while. Research that needs dozens of sources, a long document to process, or a recurring report that has to be ready by morning are all jobs that used to be awkward. Now they fit into the gaps in your day. Start the task before a meeting, check in after lunch, and the output is waiting.
There is also a timeline worth knowing. On October 6, 2026, new Cowork tasks on Pro and Max plans started running in the cloud by default. The old “Only on your computer” setting was removed, so on those plans there is no switch to choose where a task runs. Tasks that were already running locally before that date stay local until they finish.
2. Your Session Follows You Across Desktop, Web, and Mobile
The second big change is less flashy but just as useful. Your sessions and files now live with your Claude account instead of one device.
In practice, that means you can start a task on your desktop, then open the same session on the web or your phone to check progress, answer a question Claude asks, or redirect the work. When Claude finishes or needs your input, you get a notification on your phone.
Imagine you’re on a train, and a task you started that morning needs one quick decision. Instead of waiting until you are back at your desk, you open the session on mobile, answer in a sentence, and Claude carries on. That is a different relationship with your work. The task is no longer tied to a chair.
Cowork is available on paid plans. Desktop works across all of them, while web and mobile are available on Pro, Max, and Team plans (Team is in beta), plus Enterprise when an owner enables it. There is also a Cowork experience in the Claude in Chrome side panel.
Quick pause here. If you want to go beyond the basics and learn Claude in detail instead of picking it up piece by piece, The Ultimate Claude Toolkit is built for exactly that.
👉 [See What’s Inside the Toolkit]
3. Cloud Tasks vs. Tasks That Touch Your Local Files
This is the part most people miss, and it is the one that can trip you up.
A cloud task can freely reach things that also live in the cloud. That includes your connectors, like email, calendar, and cloud storage, plus files saved to your Claude account. It does not automatically reach the folders sitting on your computer.
Here is how it works. Your local folders stay on your machine. Claude can only reach folders you have connected, and only through the Claude Desktop app, and only while that app is open. When a task needs a specific file from your computer, Claude fetches a copy of just that file for the session.
So what happens if you close the app? The session keeps running, but it cannot reach your local files. Local connectors, browser use, and computer use (where Claude clicks and types on your screen) follow the same rule. They need the desktop app open on your computer.
Scheduled tasks add one more wrinkle. They run in the cloud with no device online, which is great for recurring work, but it also means a scheduled task that depends on a folder on your laptop will have nothing to read while the laptop sleeps. The simple fix is to keep a task’s inputs somewhere the cloud can reach, like a connected cloud storage account.
Get Mubashir Burfat’s stories in your inbox
Join Medium for free to get updates from this writer.
A good mental model is this. Cloud tasks are like a colleague working from the office while you are away. They can use everything in the shared drive. They cannot walk into your home and open your filing cabinet.
If a task absolutely has to run only on your computer, Anthropic points people to Claude Code in the desktop app, which runs locally and keeps your folders and history there.
4. The Kinds of Work That Benefit Most From Background Execution
Not every task gains from running while you are away. These are the ones that do.
Long research jobs are the obvious winner. A task like “gather and compare the main approaches to this topic, then write a structured summary with sources” takes time, needs no hand-holding, and is perfect to start and walk away from.
Recurring reports are another. Because scheduled tasks no longer need your computer awake, a weekly summary or a Monday morning briefing can simply be ready when you sit down. Each scheduled run becomes its own session, so you read the result whenever it suits you.
Inbox and calendar work fits well too, since connectors live in the cloud. Imagine you’re heading into a busy week and you ask Claude to go through the last few days of messages from one client and write a short brief of open questions. That is the kind of job that used to eat the first hour of your morning.
Document processing is a strong candidate as well. Cleaning up notes, drafting first versions, turning rough material into a structured document, or reviewing a pile of files stored in your cloud drive are all tasks where you care about the result, not about watching the process.
The pattern across all of these is the same. The task is well defined, takes more than a few minutes, and does not need you to make decisions every thirty seconds.
5. Work That Still Needs You
Honest coverage matters here, so a few reality checks.
Anything that depends on files only living on your laptop will wait for your desktop app to be open. Anything that involves a decision with real consequences, like sending something to a client, moving money, or deleting data, deserves a review step before it goes out. Handing off a task is not the same as handing off responsibility for the result.
Also, tasks that need quick back and forth, like brainstorming or editing something you can only judge by feel, are still better done with you in the room. Background execution rewards clarity. If you cannot describe what “done” looks like, the task will probably need steering anyway.
One more point on safety. Anthropic has a dedicated guide on using Cowork safely, and it is worth reading before you give any agent access to connected accounts. Start with low-stakes tasks, and expand as you build trust.
6. How to Start Delegating Without Regret
Here is a simple way to ease in.
Pick one task you do repeatedly that costs you thirty minutes or more. Write down what the finished result should look like in two or three sentences. Be specific about the inputs, the output, and anything Claude should avoid.
Run it once while you watch, so you can see how Claude approaches it. Then run it again, close the laptop, and check the result from your phone. If the output is solid, schedule it. If something is off, adjust your instructions and test again.
Make sure the inputs live where the cloud can reach them. If a task needs a file, put that file in a connected cloud location instead of a laptop folder. That single habit prevents most of the “why did my scheduled task skip last night” moments.
And keep a quick review habit. Skim the output, check anything with numbers or deadlines against the original, and only then trust it enough to move on.
The Bigger Shift
For a long time, using AI meant sitting in front of it. You typed, waited, read, and typed again. Cloud execution changes the question. Instead of “how do I get an answer,” the question becomes “what can I hand off and trust to come back finished?”
That is a quieter shift than a flashy new model, but it is the one that gives you hours back. The people who benefit most will not be the ones with the cleverest prompts. They will be the ones who learn which work to delegate, how to describe it clearly, and how to review the results quickly.
And if you want to build those skills properly, with the depth to use Claude well instead of figuring it all out alone, The Ultimate Claude Toolkit is there for exactly that. [Grab it here.]
See you in the next one.
Mubashir :)
P.S. Want more practical AI tools, workflows, and honest reviews delivered straight to your inbox? [Join my newsletter here.] And drop a comment below. What is the first task you would hand off to Claude?
