Claude Cowork Scheduled Tasks: The Setup Guide

[Operator’s read] I point non-technical friends and clients at Claude Cowork as the no-code on-ramp into agents — I cover the basics in the beginner’s guide to Cowork and Codex. Scheduled tasks are the feature that turns Cowork from “a place to ask for one-off help” into “a system that quietly does recurring work for you.” This is the setup guide I’d hand that same friend once they’re ready for it.

Table of contents

Open Table of contents

• What a Cowork scheduled task actually is
• Two ways to set one up
• Cadence: match it to how fast the thing changes
• Approval mode is the setting that actually matters
• The one thing that limits your cadence: cloud vs. local
• Five recurring jobs worth automating first
• Setup mistakes that waste the automation
• Claude Cowork scheduled tasks — FAQ
  • Do I need to be a developer to use Cowork scheduled tasks?
  • Which plans include scheduled tasks?
  • Does a scheduled task keep running if I close my laptop?
  • How is this different from the scheduled tasks in the regular Claude app or Claude Code?
  • What’s a good first scheduled task to set up?

What a Cowork scheduled task actually is

A regular Cowork task is a conversation: you describe what you need, Claude does it, you review the result, done. A scheduled task is the same thing minus the “you ask” part. You write the instructions once, pick how often they should run, and Claude fires that exact task on its own from then on — a Monday sales recap, a Friday client update draft, a weekly competitor scan — without you opening the app first.

Anthropic shipped scheduled tasks in Cowork in February 2026, and in July 2026 moved execution fully to the cloud: a scheduled task now runs as its own session on Anthropic’s servers, so it fires on schedule whether your laptop is open, asleep, or a thousand miles away. That distinction matters more than it sounds like it should — it’s the difference between an automation you can actually rely on and one that quietly stops the week you forget to leave your computer on.

Two ways to set one up

Cowork gives you two paths into the same feature, and which one you use depends on how clearly you already know what you want.

Create with Claude. You describe the job in plain language — “every Monday morning, pull last week’s sales numbers from my sheet and write me a five-bullet recap” — and Claude asks clarifying questions and turns your answers into the finished task, cadence included. Start here if you haven’t written an agent prompt before.

Set up manually. You fill in the task name, the exact prompt, the approval mode, the frequency, the model, and which folder or files it should have access to, all yourself. Use this once you already know precisely what you want — it’s faster than a back-and-forth once you’ve done it a few times.

Either way, the task ends up in the same place: the Scheduled section of the sidebar, where you can see upcoming and past runs, pause or resume a task, edit its instructions or cadence, delete it, or trigger a run manually to test a change before it goes live on schedule.

Cadence: match it to how fast the thing changes

The options are hourly, daily, weekly, weekdays-only, or manual/on-demand. The mistake I see most is picking the cadence that sounds impressive instead of the one that matches reality.

If the data behind your task updates weekly, an hourly schedule doesn’t get you fresher answers — it just runs the same summary twenty-three extra times and burns your attention re-reading it. Match the schedule to the actual refresh rate of the thing you’re summarizing: a sales dashboard that updates nightly gets a daily task; a competitor’s blog that posts twice a month gets a weekly one, not a daily one.

Approval mode is the setting that actually matters

This is the one setting in the manual setup that decides whether a scheduled task is safe to leave running unattended: does it hand you a draft to review, or does it act on its own?

For anything that leaves your business — an email to a client, a post to a shared channel, an update to a live document — set the task to produce output for your review, not to send or publish automatically. For anything reversible and internal — a research summary, a spreadsheet analysis you’ll read yourself, a draft you were always going to edit anyway — full autonomy is fine and saves you a step. The test isn’t “is this task trustworthy,” it’s “what does it cost me if this one run is wrong and nobody catches it before it goes out.” Reversible and internal: let it run. Outward-facing or hard to undo: keep a human in the loop.

The one thing that limits your cadence: cloud vs. local

Scheduled tasks run in the cloud by default, which is what makes “even when your laptop is closed” true. But if the task needs a local file or a local app open on your computer — a folder that only lives on your machine, a desktop application Cowork has to interact with directly — it can only run while your computer is on and awake, cloud execution or not.

Practically: if you want a task that genuinely runs itself while you’re on a plane or asleep, keep its inputs in connected tools and cloud-saved files (a shared drive, a connected spreadsheet, a Slack channel), not in a folder that only exists on your laptop. The moment a task needs something local, you’ve quietly turned “recurring automation” back into “recurring automation, as long as my laptop is on.”

Five recurring jobs worth automating first

Pick one of these to start, not all five — the point of a first scheduled task is to prove the pattern works before you stack five of them.

1. The Monday sales recap. Pull last week’s numbers from wherever they live and produce a five-bullet summary before your Monday meeting.
2. The Friday client update draft. A weekly progress note for an ongoing client, drafted for your review and edit — never sent automatically.
3. The weekly competitor scan. Check a competitor’s pricing page, blog, or changelog once a week and flag only what changed.
4. The daily inbox triage. A morning pass that groups yesterday’s emails into “needs a reply today,” “can wait,” and “safe to archive” — a summary, not an auto-responder.
5. The overnight research pull. A long research or analysis job that runs while you sleep so the result is waiting for you in the morning, instead of eating an hour of your day.

Setup mistakes that waste the automation

• Under-specifying the prompt. A scheduled task can’t ask you a follow-up question mid-run — it fires and does exactly what you wrote, nothing more. State the format, the source, and what to do in the edge case (“if the sheet has no new rows, say so instead of guessing”) before you save it.
• Skipping the manual test run. Trigger the task by hand once before trusting the schedule. If the output isn’t right when you run it on demand, it won’t magically become right at 7 AM on a cron.
• Auto-run on anything outward-facing. The fastest way to turn a useful automation into an apology email is letting a scheduled task publish or send without your review.
• Ignoring the first few runs. Sources change format, connectors get disconnected, folders get renamed. Check the run history for the first week or two, then trust it and stop watching.

Claude Cowork scheduled tasks — FAQ

Do I need to be a developer to use Cowork scheduled tasks?

No. Scheduled tasks are built into the Cowork interface — you write the instructions in plain English and pick a cadence from a menu. That’s the entire point of the no-code path: the skill that matters is writing a clear, fully-specified prompt, not writing code. See the “Create with Claude” flow above if you’d rather be walked through it than fill in the fields yourself.

Which plans include scheduled tasks?

They’re available on all paid plans — Pro, Max, Team, and Enterprise — with beta availability rolling out across desktop, web, and mobile. If you’re starting from scratch, Claude’s plans start here.

Does a scheduled task keep running if I close my laptop?

Yes, as of the July 2026 update — a scheduled task runs as its own cloud session, independent of your device, as long as everything it needs (files, connectors) is also cloud-based rather than local-only.

How is this different from the scheduled tasks in the regular Claude app or Claude Code?

Same underlying idea — a saved prompt plus a cadence — different surface. The consumer Claude app’s scheduled tasks and Claude Code’s cloud routines are aimed at developers and power users automating code or personal research; Cowork’s version is built for business tasks that touch your files, spreadsheets, and connected tools with no code involved. I cover the developer-facing versions in how to use Claude scheduled tasks.

What’s a good first scheduled task to set up?

Something you already do by hand every week, low-stakes, and easy to check at a glance — the Monday sales recap or the weekly competitor scan above are both good starting points. Get one running well before you automate anything with real consequences if it’s wrong.