Every scheduled AI task used to come with the same catch. It only ran if your laptop was open at that exact minute. Close the lid to grab coffee and the run got skipped, no error, no notification, just silence where a task should have fired. That part just changed, and it changes what these tasks are actually good for.
A contributor over on r/PromptEngineering broke down exactly what shifted and which routines are worth building first. The short version: routines now run on Anthropic’s own servers instead of your machine, so they fire whether your laptop is open, asleep, or zipped in a bag at the airport. That’s the whole unlock. A scheduled task stops being tied to your uptime and starts behaving like an actual background employee instead of a script that only works when you happen to be sitting there babysitting it.
Here’s the fast version if you want to skip ahead: open the desktop app, go to Code, then Routines. Set each one to Cloud, not Local. Write specific instructions, not vague ones. Turn on notifications so you actually see the results. That’s the whole system, and you can have the first routine live in under five minutes once you know where the toggle lives.
Old way vs. new way
The old way meant a routine was only as reliable as your uptime. Miss the window, miss the run, and you’d never know unless you happened to check. Say you set something to run at 5pm and you’re mid-commute, laptop closed in your bag. That run just doesn’t happen, and nothing tells you it didn’t happen. It made scheduled tasks feel like a party trick instead of something you could depend on, the kind of thing you’d show someone once and then quietly stop using because it kept letting you down.
The new way flips that. Once a routine is set to Cloud, it lives on Anthropic’s infrastructure and runs on schedule no matter what your machine is doing, whether that’s off, asleep, or halfway through a system update. According to the original poster, the location is the desktop app, under Code, then Routines on the left. Ignore the Code label, it’s plain English instructions on a timer, nothing technical required. You’re not writing a script, you’re writing a sentence and telling it when to run.
⚙️ The one setting everyone misses
Top right of the routine screen there’s a toggle, and it defaults in a way that trips people up. Local means the routine only runs when your machine happens to be awake at that moment, same limitation as before, just hiding behind a new interface. A closed laptop equals a skipped run, and the author called this out as the number one reason people think the feature is broken, when really it’s just one setting away from working. Switch it to Cloud and the problem disappears completely.
Three routines worth setting up
The author shared three that earn their spot on a schedule, prompts included exactly as written so you can copy them straight in, no editing needed to get started.
Follow-up catcher, daily at 5pm:
Check my sent email for anyone I said I’d follow up with and haven’t, and send me a short list of who I owe a reply or a next step, so nothing slips.
This is the standout of the three. Everyone has a handful of people they told they’d get back to and didn’t, and one commenter on the thread put it well: their inbox is a graveyard of “I’ll circle back on that.” Those are usually the threads with actual money attached, a client waiting on a proposal, a partnership that stalled because nobody replied, so catching them daily instead of never is worth more than it sounds.
Weekly numbers, Fridays at 4pm:
Pull this week’s activity from my connected apps, build a short report of what happened and what’s still open, compare it to last week, and email it to me.
Sunday planner, Sundays at 6pm:
Look at my calendar and open tasks for the week ahead and email me a prioritized list of what I need to get done, most important first, with anything time-sensitive flagged.
Two habits that decide whether it actually works
First, turn on notifications under Settings, then Notifications. Skip that step and routines run silently in the background, doing useful work you never see and never trust, which defeats the entire point of setting one up in the first place.
Second, be specific about the output you want. “Summarize my inbox” technically works, but “5 lines, most urgent first, flag anything needing a reply today” works a lot better. The difference compounds because you get that improvement every single day the routine fires, not just once, so a little extra precision up front pays out on autopilot for weeks.
Start slow, then trust it
The author’s advice here is worth repeating: begin with read-and-summarize routines before setting up anything that sends messages or changes things on its own. A summary that’s slightly off costs you nothing but a glance. A routine that fires an email unattended is a different kind of risk entirely. Keep those on draft-for-approval until you’ve watched them run enough times to trust the output.
If you’re already running a few AI workflows, this is worth an afternoon to set up properly. Start with the follow-up catcher, watch it for a week, then layer on the weekly report and the Sunday planner once you trust the pattern. Head over to the original thread if you want to see the full back-and-forth and the rest of the community’s reactions.
claude can now run tasks on a schedule in the cloud with your laptop shut. i have one that catches every follow-up i said i’d do and forgot
by u/Professional-Rest138 in PromptEngineering