Scheduled Tasks are the one feature under performers and over achievers love. From daily briefings to weekly web scraping, scheduled tasks get shit done while you’re at the gym (or sleeping in).

But as with most Claude features, there are more than a few nuances you’ll need to keep in mind before scheduling your daily 9 a.m. words of affirmation.

Three products, one word.

Cowork Scheduled Tasks, Claude Code Routines, and a local-only subset of Cowork tasks all get called “scheduled.” One label, three different execution environments. Three teams at Anthropic, apparently, landed on the same word independently.

So before we go any further, let’s sort out which one you actually need.

Cowork Scheduled Tasks are the general-purpose version you’ll use 90% of the time. They’re recurring or one-off tasks built around a prompt, your connections, and files saved to your Claude account. You can access Cowork through the desktop app, and as of August 2026, it’s also rolling out on the web, starting with Max and expanding to more plans from there. Scheduled Tasks sit behind paid tiers including Pro, Max, Team, and Enterprise, subject to rollout and your organization’s settings.

Claude Code Routines are a separate, narrower product available through Claude Code. They’re automations tied to a code repository and can be triggered on a schedule, through an API, or by a GitHub event. You’ll find them at Claude Code on the web, assuming your account has access.

The third lane isn’t really its own product. It’s a subset of Cowork tasks that need something sitting on your machine specifically, like a local Excel file or PowerPoint presentation.

You’ll probably use the first bucket most often. But for actually planning your week, that third bucket is the one you need to pay the most attention to.

A fresh start each time.

Every Cowork scheduled task is built from two inputs: a prompt and a schedule — recurring ("weekdays at 7am") or one-off ("tomorrow at 3pm"). At each fire, Claude opens a fresh session, works through the prompt with whatever connectors you've attached — Gmail, Google Drive, Apify, web search — and generates the result as a notification you open on your own time.

Scheduled Tasks don’t “evolve” or iterate on their own. If last week’s run surfaced something you want this week’s run to reference, it won’t, unless that context has been explicitly written into the prompt.

To solve for this, I suggest saving each recurring task as a Skill. After each scheduled run, review the output and, if anything should carry forward, instruct Claude to update the Skill accordingly. That way, the task/schedule itself stays static, but the underlying instructions and context can evolve over time.

Your laptop can sleep, sometimes.

Ok, listen up, because this nuance is key to understand.

Scheduled Tasks in Cowork run on Anthropic’s servers, not your laptop. Set one up and it’ll keep its cadence whether your computer is asleep, turned off, or the desktop app is closed, regardless of whether you created the task on web or desktop.

The exception is tasks that depend on a local file or app. Those require your machine to be awake and online because Claude needs to actually reach them, and it can’t reach your hard drive from a server.

Setting one up: a typical Monday morning.

Situation. Your inbox fills up over the weekend, and Monday's standup starts before you’ve had time to sort what's actually urgent.

Information gathered. The task needs the Gmail connector, not a local folder, so it qualifies for the cloud lane by default — nothing about it depends on your laptop being on at 6:45am. It can be started three ways: a new chat with Cowork toggled on, a request inside an existing Cowork session, or the "Scheduled" tab in the sidebar directly.

Step-by-step, taking the sidebar route: open "Scheduled," hit "New task," and choose "Create with Claude" for a conversational setup or "Manual task" to fill in the fields directly. Either path asks for the same four things — what the task should do (scan the inbox, flag anything from the controller or tied to the close checklist), how often it runs (weekdays), what time (early enough to read before standup), and how the output should look (a short chat summary reads faster than a full email that early).

Output. A notification with your daily briefing waiting before standup, produced by a session that ran and closed on its own, with nothing local required to make it happen.

Save your doubloons.

Credits aren't flat across the day. A task scheduled for 9am draws more credits than the same task at 3am, because 9am is high-traffic and 3am isn't (unless you’re in Ibiza).

It's a small lever, but it's a free one — nudging a non-urgent recurring task an hour or two off the peak costs you nothing except mild inconvenience.

A key unlock.

Scheduled Tasks are one of my favorite features in Claude. I used to think scheduling an email campaign was super cool. Now I can schedule virtually any task to run passively in the background while I’m doom scrolling.