How to Schedule Recurring Tasks in Claude Cowork

Summary:

1. Set up three recurring tasks that run daily without your involvement.
2. Solve the laptop-closed problem with scheduled wake times.
3. Build a monitoring log that catches silent failures in 10 seconds.
4. Copy-paste prompts for morning email, afternoon data check, and end-of-day report.

The number one question about Claude Cowork on Reddit: “How do you keep it running constantly? I only have a laptop and the moment the laptop is closed Cowork is also gone.”

Here’s the thing: you don’t need it running constantly. You need it running at specific times. Three daily tasks, 40 minutes of total Claude working time, zero minutes of your time for the tasks themselves.

How do you solve the laptop-closed problem?

The Claude Desktop app must be open and your Mac must be awake for tasks to run. Close the lid, tasks stop. Three solutions:

# Solution 1: Prevent sleep (free)
# System Settings > Energy > "Prevent automatic sleeping
# when the display is off" → ON
# Limitation: MacBook must be plugged in with lid open

# Solution 2: Schedule wake times (free, recommended)
# System Settings > Energy > Schedule
# Set wake time to 5:45am (15 min before first task)
# Add Claude Desktop to Login Items:
# System Settings > General > Login Items > add Claude Desktop

# Solution 3: Dedicated Mac Mini ($200-400 used)
# Always on, always running. Same approach OpenClaw users take.
# Overkill for most people. Use Solution 2 first.

Solution 2 is what I use. Mac wakes at 5:45am, Claude Desktop launches, tasks run from 6:00-6:30am. By the time I check my phone at 6:45am, the summary is ready.

From the official Scheduled Tasks documentation:

Scheduling option	Best for
Hourly	Slack channel summaries, website monitoring
Daily	Email triage, data checks, EOD reports
Weekdays	Work tasks you don’t need on weekends
Weekly	Expense reconciliation, weekly reports
Manual (on demand)	Tasks you trigger yourself but want saved as templates

Skip behavior: If your Mac is asleep when a task is scheduled, Cowork skips it and runs automatically once your computer wakes up. You get a notification about the skipped run. Skipped runs also appear in the task’s history on the Scheduled tasks page.

This is why Solution 2 (scheduled wake times) works: your Mac wakes at 5:45am, the skipped 6:00am task fires immediately, and results are ready by the time you check.

How do you actually create a scheduled task?

Two ways. Both take under a minute.

Method 1: The /schedule command. Open any Cowork task. Type /schedule in the chat. Claude launches a scheduling skill that asks you what the task does, how often to run it, and when. Answer the questions, click “Schedule,” done.

Method 2: The Scheduled tasks page. Click “Scheduled” in the left sidebar of Claude Desktop. Click ”+ New task” in the upper right. Fill in:

Field	What to enter
Task name	”Morning Email Triage”
Description	Brief summary of what it does
Prompt	The full triage prompt (below)
Frequency	Daily, Weekdays, Weekly, Hourly, or Manual
Model	Leave default unless you have a preference
Folder	Optional: point to a working folder

Click “Save.” The task appears on your Scheduled tasks page and runs at the next scheduled time.

How do you set up the morning email triage?

Create a scheduled task (either method above) and paste this prompt. Set frequency to weekdays, time to 6:00am.

Read email-rules.txt on my Desktop. Open Safari and go to
mail.google.com. Read all unread emails. Categorize using
the rules. Draft replies for "Needs My Reply" emails.

Save inbox-summary.txt to my Desktop with: URGENT (sender,
subject, why), NEEDS MY REPLY (sender, subject, draft),
FYI (sender, subject), ARCHIVE (count only).

Archive all ARCHIVE emails. Append to task-log.txt:
[today's date] [time] email-triage [SUCCESS/FAIL] [summary]

That last line is the monitoring log. More on that below.

How do you set up the afternoon data check?

This one monitors a specific data source and alerts you to changes. Set it for 2:00pm.

Read weekly-sales.csv in my Google Drive folder. Compare it
to yesterday's snapshot (weekly-sales-snapshot.csv on my
Desktop). Report changes: new rows, deleted rows, values
that changed (old vs new).

If no changes: just say "No changes since yesterday."
Save as data-check-[today's date].txt on my Desktop.
Replace the snapshot file with today's version.

Append to task-log.txt:
[today's date] [time] data-check [SUCCESS/FAIL] [summary]

The snapshot file trick: first run has nothing to compare against. Claude creates the initial snapshot. Starting day two, comparisons work normally. To reset the baseline after intentional changes, delete the snapshot and let Claude create a fresh one.

I caught a colleague accidentally deleting three rows from a shared budget spreadsheet this way. He didn’t realize he’d done it (stray click while scrolling). The afternoon check flagged “3 rows deleted” and I restored them before end of day.

How do you set up the end-of-day report?

Set this for 5:30pm. It wraps everything up.

Compile an end-of-day report. Save as eod-report-[today's
date].md on my Desktop. Include:

1) Email activity: how many processed, how many sent, any
   urgent items still pending
2) Calendar summary for tomorrow (list meetings with times)
3) Open action items from today's inbox summary and data check
4) Files Claude created or modified today

Append to task-log.txt:
[today's date] [time] eod-report [SUCCESS/FAIL] [summary]

Monday morning is no longer a scramble. Friday’s EOD report tells you exactly what you were working on.

Here’s what your full daily schedule looks like:

5:45am  Mac wakes up, Claude Desktop launches
6:00am  Task 1: Email triage (~25 min)
6:25am  → inbox-summary.txt on your Desktop
2:00pm  Task 2: Data check (~5 min)
2:05pm  → data-check-[date].txt on your Desktop
5:30pm  Task 3: EOD report (~10 min)
5:40pm  → eod-report-[date].md on your Desktop

Three tasks. About 40 minutes of total Claude time. Zero minutes of your time for the tasks themselves. You spend ~15 minutes reviewing outputs when convenient.

How do you monitor whether tasks actually ran?

Every prompt above includes the task-log.txt line. After a week, your log looks like this:

2026-03-26 06:27 email-triage SUCCESS 127 emails, 3 urgent, 8 replies
2026-03-26 14:05 data-check SUCCESS 3 new rows, no anomalies
2026-03-26 17:42 eod-report SUCCESS 4 meetings tomorrow, 2 open items
2026-03-27 06:31 email-triage SUCCESS 94 emails, 1 urgent, 5 replies
2026-03-27 14:02 data-check SUCCESS no changes
2026-03-27 17:38 eod-report FAIL internet timeout during calendar check

One file. One line per execution. Glance at it in 10 seconds and you know if everything ran.

What to look for:

Pattern in your log	What it means	Action
5+ consecutive SUCCESS for a task	That task is stable	Relax review to spot-checks
FAIL appears	Something broke	Check Cowork chat history for the error message
A task is missing entirely	Mac was asleep or app wasn’t open	Run it manually, check your wake schedule
Data check says “3 rows deleted”	Someone changed shared data	Investigate before end of day

This log costs nothing. One extra line per prompt. It pays for itself the first time you catch a silent failure. On day 5 of running my tasks, the log showed the afternoon data check had been failing for two days because Google Drive sync had paused. Without the log, I wouldn’t have noticed until someone asked “why did you miss the sales drop?”

You can also ask Claude to analyze the log itself:

Read task-log.txt on my Desktop. Tell me: which tasks have
failed in the past 7 days, what the failure rate is for
each task, and whether any task has been missing entirely.

What broke (and the fixes)

Task produced no output. Claude hit a login screen. Your email client logged you out overnight. Fix: enable “Stay signed in” and add to the prompt: “If Gmail shows a sign-in page, tell me in the chat and stop.”

Output was wrong. Your rules file changed and the triage behaved differently. Recurring tasks use the same prompt daily, but if the prompt references a file (like email-rules.txt) and that file changed, behavior changes too. Test after any rule edit.

Mac was asleep. Scheduled wake didn’t trigger (power outage, macOS update). The task didn’t run. No retry. Fix: first thing every morning, check if the summary file exists. If not, paste the prompt manually. Takes 30 seconds.

What should you actually do?

• If you process 50+ emails daily: set up the morning triage first. It’s the highest-value recurring task for most people.
• If you track shared spreadsheets: add the afternoon data check. Catches changes nobody told you about.
• If you want the wrap-up habit: add the EOD report. Forward it to your team lead on Fridays. Zero additional effort.
• If you hit usage limits: cut the afternoon data check to weekly. Keep morning and EOD.

bottom_line

• Three daily tasks, 40 minutes of Claude time, zero minutes of your time. The morning triage alone saves most people 60-90 minutes per day.
• The laptop-closed problem has a simple fix: scheduled wake times. Your Mac wakes at 5:45am, Claude runs at 6:00am, summary is ready before your coffee.
• Add the monitoring log to every prompt. One line per task. Catches silent failures that would otherwise go unnoticed until someone asks “why did you miss this?”