When should you use it?
- You maintain a server mainly to run scheduled agent jobs
- Upkeep such as auth refreshes and health checks eats your time
- Your jobs already keep their data in a git repository
Not for: Listeners that must stay connected, such as chat bots waiting for messages; Jobs that need sub-hourly schedules if your platform doesn't offer them
What do you need, and what do you get?
You need
- A list of every cron job with what it reads and writes
- Your repository and secrets setup
- Access to cloud scheduled tasks
You get
- Each job tagged move, restructure or delete
- A migration order with git as the shared state
- A list of blockers that keep part of the server
How does it work, step by step?
- Inventory every jobWrite down each scheduled task, its inputs, outputs and why it exists.
- Find the maintenance jobsMark jobs that only exist to keep the server healthy, such as token checks and container health; they may disappear.
- Move the simple onesShift jobs whose scripts and data already live in the repo, changing only where they run and how secrets arrive.
- Restructure pipelinesTurn parallel workers into one longer sequential session where shared context improves quality, and have each run commit its output.
- Name the blockersList anything that has to keep listening, like a message daemon, and keep only that on the server.
The prompt
Our own prompt, inspired by u/jonathanmalkin on r/ClaudeCode and written to work in Claude Code, Claude and ChatGPT. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Here is my list of scheduled agent jobs with what each reads, writes and depends on: {jobs}. The target platform runs scheduled tasks in a fresh environment each time, clones my repo, and supports {schedule_limits}. Classify each job as move as-is, restructure, delete (exists only for upkeep), or blocked (needs to stay running). For restructured jobs, describe the new shape and what they commit to git. Give a migration order and a one-week comparison test for each moved job. Do not move or delete any job until I approve the plan.
Inspired by u/jonathanmalkin on r/ClaudeCode: Claude Code Cloud Scheduled Tasks. One feature away from killing my VPS.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Each cloud run starts fresh; anything not committed to the repo is lost.
- There may be no way to chain tasks, so a job that depends on another's output needs a time gap or a check.
Our take
The useful lesson here goes beyond any one product: count how much of your automation exists only to keep the automation running. Malkin found that most of his cron jobs were auth checks, secret refreshes and health reports, and a managed scheduler made them unnecessary. That's a good audit to run even if you never migrate. His second idea, letting git carry state from one run to the next, is simple and robust because every run starts from a fresh clone and leaves a commit you can inspect. Be honest about the jobs that don't fit; anything that must listen continuously is a different shape from a scheduled task. Migrate one simple job first, compare its output with the old version for a week, then move the pipelines. Keep secrets out of the repository and use the platform's secret injection. Finally, write down task dependencies explicitly, since a fresh environment won't remember that the retrospective must finish before the morning briefing starts.
Where the time goes back: Deleting jobs that only kept the system alive removes a whole category of overnight failures.
FAQ
What still needs his VPS?
Is his setup public?
Source and credit
Inspired by u/jonathanmalkin on r/ClaudeCode. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Claude Code Cloud Scheduled Tasks. One feature away from killing my VPS.
- Creator
- u/jonathanmalkin on r/ClaudeCode
- Published on
- Original date
- Mar 24, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS (desk check, not a live run in the vendor's app). Replaces an earlier templated dry-run note.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.