Claude Code Recurring Scheduled Tasks and /loop Now Run for Up to 30 Days
Claude CodeView original changelog
Recurring scheduled tasks and /loop now keep running for up to 30 days instead of 7 while their session stays alive, and Claude Code says when they will end. Tasks created before this release still end after 7 days.
Key Takeaways
- Recurring tasks and
/looplast up to 30 days, up from 7. - The session must keep running for the schedule to stay alive.
- Claude Code now states the end date of a recurring task.
- Tasks created before 2.1.330 still end at 7 days.
- Long-lived monitoring loops become practical.
- A related fix stops a skipped scheduled task notice from pointing to
/resume; it now says to start with--resume.
Longer Lifetime for Recurring Work
Claude Code 2.1.330 changed how long recurring scheduled tasks and /loop schedules last. They now run for up to 30 days instead of 7, as long as the session that owns them keeps running. This makes it practical to leave a polling or monitoring loop in a long-lived session for a month.
Clearer Expiry
Claude Code now says when a recurring task will end, so the cutoff is no longer a silent surprise.
Existing Tasks
Tasks made before the release keep the old 7-day lifetime and still end at 7 days. Only newly created recurring tasks get the 30-day window.