Claude Code Scheduled Tasks
Schedule recurring tasks locally and in the cloud easily
712 followers
Schedule recurring tasks locally and in the cloud easily
712 followers
Run recurring coding tasks with Claude Code across both your local desktop and / or cloud. Set repos, schedules, and prompts once, and let tasks execute automatically wherever they’re set to run (locally or on cloud). Ideal for continuous workflows, automation, and agent-like development.






I’m excited to hunt this because Claude Code is moving from a tool you open to an agent that actually works for you on a schedule.
What it is: Scheduled Tasks in Claude Code now across both local desktop and remote execution.
Problem → Solution: Repetitive coding and ops tasks require manual effort or complex setups (cron, scripts). Now you just write a prompt, set a schedule, and Claude handles it automatically.
What’s different: It works both on your local machine (while it’s awake) and remotely on cloud so tasks can run continuously without you needing to keep things open.
Key features:
Set repos, prompts, and schedules
Recurring task automation
Runs locally or cloud-based
Access to your code, workflows, and tools
Use cases:
Automated reports & updates
Log monitoring + PR creation
Research and data collection
File cleanup & workflow automation
Who it’s for: Devs, founders, and teams who want agent-like automation without infra overhead.
To get started:
https://claude.ai/code/scheduled
https://code.claude.com/docs/en/scheduled-tasks
https://code.claude.com/docs/en/desktop#schedule-recurring-tasks
P.S. I hunt the latest and greatest launches in tech, SaaS and AI, follow to be notified → @rohanrecommends
@rohanrecommends Love the local/cloud flexibility. And congrats. Just a quick q: how do you handle prompt drift or context loss in long-running remote schedules, like for ongoing log monitoring or PR automation?
been wanting this for a while - I've got a few repos where I manually kick off the same Claude Code prompts like 3x a week. setting schedules once and forgetting it is exactly how it should work. curious how the cloud piece handles auth - does it need separate Claude API keys per environment or does it pick up from local config somehow?
@rohanrecommends @brooke_dewitt1 @scott_white_sf
Im keen to understand this. Is this essentially an AI agent that will independently go and complete tasks?
Im currently on Max plan and have Co-Work enabled. How is scheduled tasks different?
Okan
Bridging the gap between local cron jobs and cloud environments usually requires maintaining entirely different setup scripts. I would definitely use this to manage my automated database backups so I can test the intervals locally before pushing them directly to production. The unified syntax alone will save developers a lot of unnecessary debugging time.
How is this different than the Github action and a scheduled workflow a part from the obviously much easier to setup?
Setting up cron jobs for AI tasks was genuinely painful before this. Write a prompt once, set the schedule, and let it run — locally or in the cloud. This is what "agentic" actually looks like in practice 🔥