One of Claude Code‘s most underused features is scheduled tasks — the ability to have Claude automatically run jobs on a recurring schedule without you being at your computer. Morning PR reviews, overnight log analysis, weekly dependency audits, daily reports that show up in your inbox before you even open your laptop: all possible with Claude’s scheduling features in 2026.
This guide covers the two main ways to schedule Claude — cloud scheduled tasks and desktop scheduled tasks — and walks through practical workflows that save hours per week.
Why Scheduling Matters
Most AI workflows require you to be present: open the tool, type the prompt, wait for the result, decide what to do. Scheduled Claude inverts that. You set up the job once, describe what should happen and how often, and the output shows up ready for review.
Three categories of tasks are particularly well-suited to scheduling:
- Recurring analysis: Daily metrics reports, weekly performance reviews, monthly trend analyses.
- Maintenance tasks: Dependency checks, broken-link audits, content freshness reviews.
- Watch-and-alert: Monitor a folder, website, or data source and alert when something changes.
The Two Types of Scheduled Tasks
Cloud scheduled tasks (recommended)
Per Anthropic’s documentation, cloud scheduled tasks run on Anthropic-managed infrastructure. They keep running even when your computer is off. Create them from the web, the Desktop app, or by running /schedule in the Claude Code CLI.
Best for: Truly recurring tasks that don’t need access to your local files.
Desktop scheduled tasks
Desktop scheduled tasks run on your machine. They have access to your local files and tools, which is necessary for workflows involving project folders, codebases, or desktop applications. The catch: they only run when your computer is on.
Best for: Tasks that need to read or modify local files (codebases, document folders, project state).
/loop: for in-session polling
Different from scheduled tasks: /loop repeats a prompt within your current CLI session for quick polling. Useful when you want to check something every few minutes during an active session — watching a long-running build, monitoring a deploy, polling for a file to appear.
Get More Claude Code Workflow Tips
Join our free newsletter for practical AI tutorials, tool updates, and business strategies — written for beginners, useful for everyone.
Subscribe FreeSetting Up Your First Scheduled Task
- Install Claude Code if you haven’t already. Our beginners guide walks through setup.
- Type
/schedulein Claude Code. This opens the schedule creation flow. - Describe the task in plain English: “Every weekday at 8am, check all open pull requests in this repo and email me a summary of which ones need my attention.”
- Pick cloud or desktop based on whether the task needs local files.
- Set the schedule: cron-style syntax, or simple English like “every Tuesday at 9am.”
- Choose output destination: email, Slack, a file in your project, or a CLI notification next time you open Claude Code.
- Save and walk away. Claude runs on schedule.
5 Scheduled Tasks Worth Setting Up
1. Morning brief
“Every weekday at 7am, summarize: my top 10 unread Slack messages, any urgent Linear tickets assigned to me, and any broken-window CI failures from overnight.” Delivered to your inbox before your first coffee.
2. Weekly dependency audit
“Every Friday at 4pm, check this project’s dependencies for security vulnerabilities and version mismatches. Email me a report of anything that needs attention.”
3. Content calendar check
“Every Monday at 9am, check the content calendar. Tell me what’s scheduled this week, what’s missing, and what drafts need review.” Pair with the Content Repurposer plugin to automatically generate fresh social formats for scheduled posts.
4. Competitor monitoring
“Every Monday morning, visit these 5 competitor websites, flag any material changes since last week, and send me a summary.”
5. Documentation health
“Every Sunday at 6pm, check the docs folder for pages older than 60 days. List the ones most in need of updates based on code changes since they were written.”
10 Claude Scheduling Plays Most Users Have Not Tried
You have one or two scheduled tasks running. The 10 plays below produce real ongoing leverage from Claude scheduling in 2026.
1. Daily news digest matched to your interests
Claude pulls feeds from sources you trust each morning, produces a one-page digest of what matters for your work today. Skip the doomscroll.
2. Calendar-prep packet 2 hours before each meeting
Two hours before your next meeting, scheduled task pulls attendee context, recent communications, and shared docs into a prep packet. Walk in prepared, not blind.
3. Weekly project-status auto-summary
Friday afternoon scheduled task summarizes your week from Jira plus Slack plus Drive. Status reports take 0 minutes; you spend that time on actual work.
4. Monthly metrics-and-trends review
First of every month, Claude pulls last-month metrics across your tools (analytics, CRM, accounting) and produces a structured review with month-over-month trends. Decisions improve when data shows up automatically.
5. Quarterly competitor-monitoring report
Once a quarter, scheduled task scrapes competitor sites, social, news, and produces a positioning-and-changes report. Strategic awareness without manual surveillance.
6. Birthday and milestone celebrations from your CRM
Daily scheduled task surfaces clients with anniversaries, birthdays, or business-milestone dates today. Drafts a personal note. Relationship maintenance without remembering.
7. Inbox-zero-Sunday weekly review
Sunday evening scheduled task reviews open email threads, surfaces stale ones, drafts triage proposals. Monday inbox starts cleaner.
8. Scheduled coaching from your journal
If you journal in Obsidian or Notion, scheduled task reviews the last week of entries weekly, surfaces themes, asks reflection questions. Self-coaching becomes habitual.
9. SLA-monitoring with proactive client comms
For service businesses, scheduled task monitors SLA exposure, drafts proactive client communications when breach risk rises. Trust climbs even when service does not.
10. Annual review automation
End-of-year scheduled task assembles your year: wins, losses, learnings, decisions. Year-end retrospection becomes deliberate instead of forgotten.
Integration With Other Automation Tools
Claude scheduling is most powerful when combined with broader automation:
- Zapier + Claude — Trigger Claude workflows from Zapier, or have Claude push results to Zapier for downstream automations.
- MCP (Model Context Protocol) — Connect Claude to external tools via MCP servers. Your scheduled task can query databases, call APIs, or interact with SaaS tools.
- Slack/Discord webhooks — Route scheduled outputs into team channels for shared visibility.
- Email — Simplest output method. Great for personal workflows.
For a full automation stack comparison, see our best AI for automating work guide.
Common Scheduling Mistakes
- Scheduling too often. A task that runs every hour can feel like progress but creates notification fatigue. Start daily or weekly; increase frequency only if needed.
- Not reviewing early runs. The first 3-5 runs of any scheduled task reveal issues. Review them. Tune the prompt. Then let it run unattended.
- Using desktop tasks when cloud would work. Desktop tasks only run when your computer is on. For reliable recurring work, cloud is almost always right.
- Forgetting about them. Audit your scheduled tasks quarterly. Kill ones you’re ignoring. The best kept-running tasks are the ones you still read.
- Not setting up failure alerts. Scheduled tasks fail silently by default. Configure email or Slack alerts for errors so you know when something breaks.
Your First Scheduled Task This Week
- Pick your most repetitive recurring task. Weekly reports, daily standups, Monday planning.
- Write the prompt for one run, manually. Get it producing the output you want.
- In Claude Code, type
/schedule. Paste the prompt. - Pick the cadence. Start conservative (weekly is fine for most things).
- Choose output destination. Email, Slack, or a file.
- Review the first 2-3 runs carefully. Tune the prompt if needed.
- After it runs clean for 2 weeks, add a second scheduled task.
Frequently Asked Questions
Do scheduled tasks cost extra?
They count against your normal Claude usage. If you’re on Pro ($20/mo), the scheduled tasks are included up to your plan limits. For very high-volume scheduling, you may hit limits and want to move to Max or Enterprise tiers.
Can I see what scheduled tasks I have running?
Yes. In Claude Code, type /schedule list. You can also manage them from the Desktop app or web interface.
What if a task fails?
Claude retries failures and logs errors. You can configure failure notifications to be sent to email or Slack so you know when something went wrong. For desktop tasks, failures often mean the computer was off — switch to cloud tasks if reliability matters.
Can scheduled tasks modify my files?
Yes, desktop scheduled tasks can. Use permission controls in CLAUDE.md to restrict what actions are allowed — for example, “can read but not delete files” or “can only write to /output folder.”
How is this different from traditional cron?
Traditional cron runs shell commands on a schedule. Claude scheduling runs intelligent agent tasks — the prompt is plain English, Claude decides how to execute it, and the result can involve reasoning rather than just running a script. Think of it as cron for tasks that require judgment.
The Bottom Line
Scheduled tasks move Claude from “AI I open when I need help” to “AI that works in the background on my behalf.” For recurring workflows, this is the difference between saving a few minutes per task and saving hours per week.
Start with one scheduled task that eats the most time in your week. Get it reliable. Add more once that one has run for two weeks without issues.
To find more places AI could compress your work, install the free 44% Rule plugin — based on Harvard research, it audits your workflow for automation opportunities you might be missing.
Get Smarter About AI Every Morning
Free daily newsletter — one story, one tool, one tip. Plain English, no jargon.
Free forever. Unsubscribe anytime.