◉CLAUDE LABJP
●CC 2.1.328 — Claude Code 2.1.328 (11/19) fixes saving a scheduled task sometimes wiping your other tasks●SONNET 4.5 — Retires on the Claude API on 11/30, 10 days left. Sweep model IDs in code and saved settings in one pass●USAGE — Users report usage limits running out 3–5x faster since the week of Nov 9●NEW — One Source of Truth for MCP Config Across Claude Code and Gemini CLI●GEMINI API — The Gemini API now has tool retrieval (Preview), loading tool definitions only when needed●CREDIT — Seeing a low Credit balance? First check which billing account it refers to●CC 2.1.328 — Claude Code 2.1.328 (11/19) fixes saving a scheduled task sometimes wiping your other tasks●SONNET 4.5 — Retires on the Claude API on 11/30, 10 days left. Sweep model IDs in code and saved settings in one pass●USAGE — Users report usage limits running out 3–5x faster since the week of Nov 9●NEW — One Source of Truth for MCP Config Across Claude Code and Gemini CLI●GEMINI API — The Gemini API now has tool retrieval (Preview), loading tool definitions only when needed●CREDIT — Seeing a low Credit balance? First check which billing account it refers to
Articles/Cowork
◈ Cowork/2026-03-19Intermediate

Claude Cowork Scheduled Tasks — Recurring Runs, Reminders, and Auto-Reports

How to set up recurring execution, one-time reminders, and automatic reports with Claude Cowork's scheduled tasks. From cron syntax to dry runs, timing spread, and idempotent prompts, with the lessons that only show up in real operation.

Cowork69Scheduled Tasks20Automation44Recurring ExecutionRemindersReportsMCP Connectors3

✦ Premium Article

Setting Up and Running Claude Cowork Scheduled Tasks

You gather the same information every morning, then build the same report by hand every Friday afternoon. Keep doing "the same work at the same time" long enough and one day it occurs to you: maybe I don't have to be the one doing this. Claude Cowork's scheduled tasks are the feature that kicks in at exactly that moment.

That said, setting one up doesn't mean it quietly takes care of itself. Automation is wonderful, but a small misreading of an instruction can pile up, dozens of times over, while no one is watching. Alongside the setup steps, I'll fold in the operational lessons that stuck with me from keeping tasks running unattended.

Three Patterns: Recurring, One-Time, Ad-hoc

A scheduled task automatically launches a Claude session at the time you specify and runs the prompt you configured. There are three ways it can fire.

Recurring. Repeats at intervals set by a cron expression—daily at 9am, every Monday, the 1st of each month.

One-time. Runs once on a specific date and time. "Remind me tomorrow at 3pm" works this way, and the task auto-disables after it fires.

Ad-hoc. No schedule; you trigger it by hand when needed. Handy for templated work you want to run on demand.

The first thing to decide is whether the job repeats or happens once. Get this backward and a one-shot notification ends up arriving every single day.

✦

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN
✦Designing recurring, one-time, and ad-hoc tasks with copy-paste-ready prompts for each pattern
✦Reading cron syntax in your local timezone, plus the weekday gotcha that quietly breaks schedules
✦Operational lessons—off-peak timing, manual dry runs, and idempotent prompts—that keep unattended runs stable
Secure payment via Stripe · Cancel anytime
✦

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

or
Unlock all articles with Membership →
Share

Thank You for Reading

Claude Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • ✦Copy-paste ready implementation code
  • ✦New advanced guides published daily
  • ✦$5/mo or $10 for lifetime access
View Membership →

Related Articles

◈ Cowork2026-09-18
How I decide between Cowork and Claude Code: by where approvals land
Cowork and Claude Code run the same Claude, so I stopped comparing features and started sorting work by one question: can a human approval interrupt this step, or not? Here is the line I draw and the code I keep on the unattended side.
◈ Cowork2026-11-20
Copy Your Scheduled Tasks' Prompts and Times Once a Week, So You Can Restore Them If They Vanish
Scheduled tasks can disappear or need rescheduling after an app update or a save that fails to read its file. Here is a weekly habit for keeping three things—prompt, schedule, and connected folders—in your own folder, plus a small script that tells you which copies changed since last week.
◈ Cowork2026-10-26
I Linted 36 Unattended-Run Prompts: All 7 'Use This Tool' Hits Turned Out to Be Bans
One permission dialog is enough to stall an unattended task, because nobody is there to click it. This note covers a lint script that counts prompt lines that tell the task to use such a tool, why a banned-word grep gave seven false alarms, and how matching on word stems fixed it.