Practical Use Case 1: Morning Information Collection

Daily 9am collects latest information on tech topics of interest, creates summary.

Task name: morning-tech-digest, description: "Daily tech news digest generation."

Prompt design:

Search past 24 hours for latest information on these topics:

Topics:
- Claude/Anthropic latest updates
- New AI agent tools and frameworks
- Apple/Google developer news

Collect information and consolidate in markdown format:

Filename: tech-digest-{today's-date}.md

Format:
# Tech Digest {today's-date}

## Major News
(Summarize each news in 2-3 sentences)

## Key Points
(1 paragraph on most important developments)

Save file to workspace folder.

Set cron to 0 9 * * * (daily 9am).

Prompt Design Tips

Scheduled task prompts must convey intent completely—unlike interactive conversation, context doesn't carry over between sessions.

Specify output format clearly. Write concrete filename patterns, save location, format. Claude starts fresh each execution.

Avoid ambiguity. Instead of "recent news," say "past 24 hours." Instead of "several," say "maximum 5." Quantify precisely.

Include error behaviors. "If no search results found, note this in the file." This improves stability.

Practical Use Case 2: Weekly Report Auto-Generation

Fridays 5pm generates consolidated report of workspace file changes from the week.

Check workspace folder files and retrieve those created or updated
in the past 7 days.

Create weekly report as .md file:

Filename: weekly-report-{this-friday's-date}.md

# Weekly Report ({Monday} – {Friday})

## This Week's Deliverables
- New files: {list}
- Updated files: {list}

## Work Summary
(3-5 sentences inferring main work from file content)

## Next Week
(Propose uncompleted work or next steps)

Set cron to 0 17 * * 5 (Fridays 5pm).

Practical Use Case 3: Reminders

One-time execution for reminders. In conversation, say "remind me tomorrow 2pm"—Claude auto-creates one-time task.

Internally, fireAt parameter gets ISO 8601 timestamp like 2026-03-20T14:00:00+09:00.

Reminder prompt is simple:

Remind user of this:

Reminder content: Design review meeting 3pm preparation
                  Final-check Figma prototypes

Save reminder to workspace as .md file.

MCP Connector Integration

Scheduled tasks become more powerful combined with MCP connectors. With Slack connector, save morning digest directly to Slack. With Google Drive, append weekly reports to spreadsheet.

Simply write "Post to Slack #general channel" in task prompt—connected MCP connectors execute it.

Task Management and Operations

Task Pause and Resume

Recurring tasks pause/resume via enabled flag. Pause morning digest during vacation, stop weekly reports at project milestones.

Notification Settings

Control notifyOnCompletion for current session notifications on task completion. For background tasks, disable notifications for comfort.

Execution Timing Notes

Recurring tasks include several-minute random delay for server load balancing—not exactly 9:00:00. For second-precision needs, not ideal. One-time tasks have no delay.

Mac sleep or app closure prevents execution. Next app launch may run skipped tasks.

Troubleshooting

Task not executing checklist:

Verify Cowork is running, Mac isn't sleeping. Confirm enabled is true. Check cron syntax—especially verify weekday specification (note: 0 and 7 both mean Sunday).

Overly long or complex prompts cause mid-task stops. Set each task one clear goal, split complex processes across tasks.

A Note from an Indie Developer

Key Takeaways

Scheduled tasks transform Claude Cowork from "conversation tool" to "automation platform." Delegate morning collection, weekly reporting, reminders to Claude, freeing yourself for creative work.

Start simple—morning digest—then gradually add tasks.

What You Can Automate

File Management

• Regular cleanup of the Downloads folder
• Archiving old files
• Batch file renaming

Report and Document Generation

• Weekly summary reports
• Graph generation from data files
• Meeting agenda preparation

Data Monitoring

• Spreadsheet anomaly checking
• File change monitoring
• Regular backups

Setting Up Schedules

Create a scheduled task in Cowork by specifying what to do and how often.

Basic Examples

"Every morning at 9am, move files older than 1 week from Downloads to the Archive folder"

"Every Monday morning, create a weekly report from last week's sales data"

Cron Expression Scheduling

For finer control, use cron expressions:

• 0 9 * * * — Every day at 9:00 AM
• 0 9 * * 1-5 — Weekdays at 9:00 AM
• 30 8 * * 1 — Every Monday at 8:30 AM
• 0 0 1 * * — First day of every month at midnight

Scheduling Lessons from Running a Solo App Business

I've developed and run iOS and Android apps on my own since 2014. The apps have grown to roughly 50 million downloads over the years, and behind them sits a steady stream of unglamorous, recurring work — refreshing image-server configuration, regenerating App Store screenshots, and so on. As I gradually moved that work onto scheduled tasks, a few lessons emerged that you won't find in the official docs.

The one that helped most was staggering the timing. When you stack several recurring tasks in the same window, their work overlaps and they end up tripping over each other. I deliberately spread my run times into off-peak hours — avoiding the 7–9am commute crush, the 12–1pm lunch window, and the 6–11pm evening peak — and simply spacing jobs 30 to 45 minutes apart through the late night and early morning noticeably cut down on dropped runs. Once you have more than a handful of tasks, just designing when each one fires buys you a lot of stability.

The second lesson: always do one manual "dry run" before you schedule anything. Automation is wonderful, but a small misreading of an instruction can quietly pile up, dozens of times over, while no one is watching. Before I register a new task, I run it by hand once and read the output line by line. I also keep a short log of what each run changed and why — being able to retrace my own steps later has saved me more times than I can count.

Best Practices

1. Automate Gradually

Start by running tasks manually to verify results, then set up the schedule once you are confident.

2. Write Clear Instructions

Be specific with task descriptions. Instead of "organize files," say "move .pdf files from Downloads to Documents/PDFs."

3. Check Results Regularly

Periodically review automated task results to ensure everything works as expected.

Important Notes

• Scheduled tasks only run while the Cowork desktop app is active
• Be careful with tasks that involve deleting important files
• Run new tasks manually once before scheduling to verify behavior

Looking back

Scheduled tasks free you from repetitive daily work. Start small and gradually expand the scope of automation.