Claude Cowork left the desktop. Here's what that buys a consultant.

Two weeks ago we made the case for pointing Claude at a folder instead of pasting your practice into a chat box, piece by piece, forever. The one honest caveat in that piece was the surface: the folder pattern lived in Claude Cowork, and Cowork lived on the desktop.

It doesn't anymore. On July 7, Anthropic announced that Cowork is rolling out to the web and to the Claude apps on iOS and Android — in beta, arriving plan by plan over several weeks. If it hasn't reached your account yet, it's coming; nothing below depends on which week you get it.

The coverage has framed this as "the AI agent goes mobile," which undersells the part that matters for a consulting practice. The phone app is not the story. The story is where the work now runs.

The actual change: the session outlives your device

Desktop Cowork works on your machine, in your folders — close the laptop mid-task and the work stops with it. The web and mobile version runs the session remotely, and Anthropic is specific about what that means: close the laptop and Claude keeps going. Scheduled tasks now run with no device online at all.

Read that second sentence again as a consultant. There is now a version of "Claude, draft the Friday updates" that runs at 6 AM Friday whether or not you've opened a computer — and the draft is waiting for your review pass when you do. The delegation pattern we've been building toward all year — brief in, deliverable out, your judgment on the review — just picked up a property it never had: it doesn't need you present for the middle.

Three concrete shapes this takes for a solo practice:

The handoff that survives the school run. You start the case-study assembly at your desk at 4:40. At 5:00 you leave. The session keeps working; when Claude hits a call only you can make, the question reaches your phone, you answer it from the parking lot, and the draft is done when you're back. Anthropic's announcement describes exactly this shape — start at your desk, check from your phone, pick up the output anywhere.

The scheduled deliverable. The recurring, known-shape work of a practice — the Friday client update, the Monday pipeline note — can now be a standing task with a schedule, not a reminder in your calendar that you race at 4:45 PM. The work runs; your job contracts to the read.

The review from anywhere. The mid-task question and the finished draft both reach the device in your pocket. The judgment half of delegation — the half we keep insisting is not optional — no longer waits for you to be at a desk.

What stays on the desktop, honestly

Anthropic's own framing keeps the desktop app as the home for deep work — and for a consultant the practical line is sharper than that: your local folders live on your machine. The web and mobile surfaces run sessions in the cloud with the files you've given your Claude account; the desktop app is what works directly in the folder structure sitting on your disk, next to your local browser and tools.

So the honest version of the workflow, today, while this is beta: the desktop remains the primary surface for folder-based client work — the workspace pattern, the inputs-and-deliverables convention, the standing instructions file. Web and mobile are, first, the continuation surfaces: where sessions you started keep running, where questions reach you, where scheduled work lands. Feature availability differs across the platforms and the beta is moving; treat the desktop as the workshop and the other surfaces as the workshop's messenger, and you'll be calibrated about right.

One more honest note: it's a beta, arriving in waves. If Cowork isn't on your web or mobile app yet, that's rollout, not a setting you've missed. Anthropic has also doubled Cowork usage limits through August 5 to mark the launch — worth knowing if you're deciding when to run your first real experiment with it.

Why this matters more than a model release

We wrote in June that a stronger model raises the return on setup — context files, standards, standing instructions. A new surface does the same thing from a different angle, and arguably harder.

Here's why. Everything the remote session does, it does from what's written down. When a session runs at 6 AM with no device online, there is no you-in-the-loop to fill gaps from memory — the session has your files and your brief, and nothing else. Vague standards that survived because you were always present to correct course stop surviving. The practices that will feel like magic on this surface are the ones that already invested in the boring assets: who you serve, what you sell and at what floor, what a finished update looks like, one context file per client.

That's the same conclusion as every piece we've written this summer, arrived at from a new direction, so we'll say it plainly once more: the durable asset is the written-down practice. Models change under you; surfaces multiply around you; the files transfer.

And there's a second-order effect worth naming for the profession. Anthropic reported that when it analyzed how people actually use Cowork, more than 90% of it wasn't software development — the biggest categories were business operations and content creation. The folder-shaped, delegated-deliverable way of working isn't a developer curiosity that consultants are borrowing anymore. It's becoming the mainstream shape of knowledge work, and the consultants who built their setup early are about to look prescient rather than eccentric.

What to do this week

If you have Cowork on desktop already: nothing changes about your workspace; add the new surfaces as they reach your account. First experiment: take the deliverable you most reliably produce late — for most consultants that's the Friday client update — and run it as a scheduled task for Friday morning instead of a 4:45 PM scramble. Review on your phone, send before lunch.

If you've been waiting because "it needs the desktop app": that reason is expiring on its own schedule. The pattern to prepare is the folder anatomy from the workspace piece — instructions, context, standards, one folder per client. Build it once; every surface Claude ships from here reads the same files.

If you want to feel the delegated-deliverable pattern before building anything: our free Friday Update Brief is one self-contained handoff — the brief, a sample week of messy notes, the reference output to compare against. It runs pasted into any Claude chat, today, on whatever surface you have. It costs your email address.

And when you're ready for the standing version — the folder with the guardrails written, four deliverable standards, six ready-to-run briefs, and a worked example you watch run before you trust it — that's the Claude Workspace Kit, $67, built for Cowork and identical in Claude Code. It's the setup this new surface was built to reward.

The chat box was a fine place to meet Claude. The desktop folder was a better place to work with it. Now the work runs whether you're at the desk or not — and the only practices positioned to collect on that are the ones written down well enough to run unsupervised. Write yours down.