I have a handful of tasks that do the same thing every day. Pulling in news and releases about innovation, AI and wine, so I stay ahead and can turn it into content. Cleaning up my mailbox, adding labels, preparing drafts so all that is left for me is to check them. Small, fixed jobs I set up carefully once in Claude Cowork, and that have been taking work off my plate ever since.
Until now there was one condition attached. My laptop had to be on and the app had to be open. If I walked away, or closed the screen, everything stopped. As of this week that condition is gone.
Anthropic is taking Cowork off the desk. What used to run only on your desktop can now be followed and steered on web and mobile too. And the part that matters most to someone who works with fixed tasks: scheduled tasks now run without your computer needing to be online. You line up a prep job for six in the morning, and by the time you sit down at your desk the work is already done.
Anthropic showed it in a short demo: watch the announcement.
What was actually announced
The essentials, so you do not have to guess:
- Cowork moves to web and mobile. You start something on your laptop, walk away, and pick it up again on your phone or in the browser. The session no longer dies when your screen closes.
- Scheduled tasks run in the cloud. They no longer need your own machine to start. That is the real shift: the work happens even when you are offline.
- You keep the last step. If Claude runs into doubt, or wants to send something, it asks for your sign-off first. It sends nothing on your behalf without you having seen it.
- Chat and Cowork move closer together. They land in the same space, with access to the same files. Less back and forth between two places.
- Who gets it now. The beta starts with Max users, the most expensive consumer plan. A wider rollout follows in the coming weeks. The doubled usage limit runs through 5 August.
Anthropic also shared numbers on how people use Cowork. Across more than a million sessions, most of it is not code but knowledge work: pulling documents together, building reports, writing. Content creation alone accounts for a sixth of all usage. That matches my own experience. Cowork has never been a coding machine for me; it is where the groundwork happens.
Where it makes a difference for me
The difference is not in what it can do, but in timing. The tasks I was running could already do plenty. What they could not do was keep going at the moments I was not there myself, and those are exactly the moments I want to use.
Take pulling in the news. In the morning I do not want to start by searching, I want to start with an overview that is already sitting there. If that task can run overnight while my laptop is off, then the first thing I see is not a blank page but a starting point. The same goes for the mailbox. Sorting it and lining up drafts does not have to wait until I sit down. It can happen before I arrive.
That is exactly where Cowork is strong: not the one-off question, but the recurring job you do again and again. Build it well once, and after that it costs you a sentence. What changes now is that the job is allowed to run without me.
I do have to admit my enthusiasm ran ahead of the news for a moment. In my head I already pictured my whole workspace in the cloud: all my Code projects synced, a backup somewhere else, every skill and connector available everywhere. That is not what was announced. Cowork is not the same thing as Claude Code, and my development projects are not part of this. It is tempting to make the announcement bigger than it is. This is about knowledge work that keeps running, not about my entire machine moving to the cloud.
The caveats
I want to sit with this part longer than the rest, because it is the side that easily gets buried.
First, and heaviest for me: the work moves from my computer to Anthropic’s. When I wrote about Dispatch earlier, the nice thing was precisely that it ran on my own machine, with my own files, and not on some anonymous server. That property is now partly reversed. If a task runs while my laptop is off, it happens somewhere else, with access to my mail, my calendar, my documents. That is not a reason to avoid it, but it is a real trade-off. Where your data sits and who can reach it is not just a detail.
Second, access. This starts with the most expensive plan and only trickles down from there. You build a way of working around something you do not hold yourself and that sits behind a price tag. Useful while it is there, but it is a dependency.
Third, the temptation to treat the human sign-off as a formality. That Claude asks for your approval before it sends anything is exactly the brake you want. But a brake only works if you use it. The more that sits ready automatically, the greater the chance that one day you just click through without looking. The value of the last step is that you actually take it.
Cowork does not so much change what the tasks can do, but when they are allowed to run. For me that is enough to finally cut loose the jobs I already had from the moment my laptop happens to be on. As long as I keep deciding what goes out the door.
Sources
- Claude Cowork on web and mobile — Anthropic, product announcement
- Anthropic brings Cowork out of the desktop and onto web and mobile — SiliconANGLE
- Anthropic will make Claude Cowork available to users via the cloud — NBC News
This piece also appeared in Dutch: Claude Cowork loopt nu door zonder mijn laptop.