Scheduled Tasks in Claude Code: Automate Recurring Work Without Writing Code (2026 Guide)
Work That Gets Done on Its Own: The Magic of Scheduled Tasks
Every morning you open your computer and do the same thing: check server logs, generate yesterday's sales report, sort new leads into a spreadsheet. Always the same. Always at the same time.
What if that work was already done by the time you turn on your computer?
That's what Claude Code's Scheduled Tasks offer — one of the most powerful features of the ecosystem Anthropic launched in February 2026.
If you want to understand the full context of why this feature exists, read Claude Channels and Remote Tasks first.
What Are Scheduled Tasks and Why Are They Different
Scheduled Tasks aren't simply "cron jobs with AI." They're something more sophisticated:
- You define the work in plain language, no YAML or cron syntax
- Claude understands the context of the task and can adapt to it
- Built-in safety guardrails prevent runaway executions
- They integrate natively into the Claude Code sidebar
The difference from a traditional automated script is that Claude can reason about the task, handle unexpected variations, and decide how to proceed when something isn't exactly as you described.
Two Modes: Desktop Tasks vs /loop
Claude Code offers two ways to schedule automatic tasks, each for a different use case.
Mode 1: Desktop Scheduled Tasks (Persistent)
These are the "real" scheduled tasks: they persist across restarts, appear in the Claude Code sidebar, and have a full configuration.
Each desktop task has:
- Name: a readable identifier for you
- Description: what it does exactly (in plain language)
- Frequency: how often it runs (daily, weekly, hourly...)
- Model: which Claude version it uses (useful for cost control)
- Working folder: the context directory for the task
How to create one:
Option A — from the sidebar:
Claude Code → Sidebar → "Scheduled" → "New task"
Option B — with the /schedule command inside any session:
/schedule
Claude will guide you with questions: what do you want it to do? How often? In which folder? No need to know cron syntax.
Example configuration:
- Name: "Daily sales report"
- Description: "Every morning at 8:00 AM, read sales data from the CSV in ~/Sales/data/, generate an executive summary with the main KPIs, and save it to ~/Reports/daily/"
- Frequency: Daily at 08:00
- Folder: ~/Sales
Mode 2: Session Tasks with /loop (Temporary)
For automations within an active session. Faster to create but they don't survive session closure.
/loop every 30 minutes: check for new files in ~/Pending and process them
Perfect for:
- Folder monitoring during a working session
- API or external service polling
- Automatic processing of incoming files
Safety Guardrails: Why They're Crucial
Anthropic designed Scheduled Tasks with a clear principle: automations must be controlled, not runaway.
Built-in guardrails:
Automatic Expiration After 3 Days
Recurring tasks automatically expire 3 days after creation. This prevents forgotten tasks from running months later.
Want them to continue? Renew them consciously. This small, intentional friction is a design decision, not a bug.
50 Concurrent Tasks Per Session Limit
Each Claude Code session supports a maximum of 50 simultaneous scheduled tasks. More than enough for any real use case, but a limit that prevents accidental runaway.
Complete Disable via Environment Variable
If you ever want to globally disable all Scheduled Tasks:
export CLAUDE_DISABLE_SCHEDULING=true
Useful in production environments where you want explicit control over what executes.
Per-Task Permissions
You can configure which actions each task can take without asking for confirmation. By default, actions that modify files outside the configured working directory require approval.
Real Use Cases That Justify the Setup
For Businesses and SMBs
- End-of-day report: summarizes sales, new customers, or support tickets each afternoon
- Email classification: moves new leads to the right folder and generates a summary
- Backup and cleanup: archives old files and removes temp files according to rules
For Developers and Technical Teams
- Log analysis: checks error logs every hour and generates an incident summary
- Build monitoring: notifies when CI/CD status changes
- Dependency updates: checks for new versions of critical packages
For Freelancers and Consultants
- Weekly work summary: generates a completed-task report to send to the client
- Project file management: organizes and archives materials from finished projects
- Meeting preparation: gathers relevant information before scheduled meetings
Combining Scheduled Tasks with the Full Ecosystem
Scheduled Tasks reach their full potential when combined with the rest of Anthropic's features:
- + Claude Channels: the scheduled task sends results via Telegram or Discord when done
- + Remote Control: approve or reject actions from mobile without being at the computer
- + Remote Cloud Sessions: longer scheduled tasks run on Anthropic's cloud
Not Sure How to Apply This to Your Business?
Scheduled Tasks are one of those cases where "how to configure it" is relatively straightforward, but "what to automate and how to design it well" requires experience.
I've helped clients identify exactly which repetitive tasks in their business are automatable, design the right flows, and implement them safely.
If you'd like to do the same for your company or project, reach out on WhatsApp. First consultation is free and no-commitment.