Automation & agents · Claude Code

Move nightly jobs and morning briefings onto cloud scheduled tasks

Idea + starter prompt, not run by us yet

For: Builders who run Claude automations on their own servers with many cron jobs

The author ran a self-hosted Claude setup with 11 cron jobs across three environments and a Slack daemon, then worked out which jobs could move to cloud scheduled tasks. Nightly reviews and the morning briefing would run in order, passing work through git. That would retire 7 of the 11 cron jobs. The always-on Slack piece stays behind because cloud tasks start fresh and cannot listen for messages.

Steps

1. List every cron job you run and mark why it exists: real work or just keeping the system alive.
2. Move the real work to scheduled tasks and let each task commit its output to git.
3. Run dependent jobs in sequence, with the earlier task's committed output as the next task's input.
4. Keep anything that must listen all day, such as a chat bot, on your own server.
5. Test each task by running it by hand and read the commit before you trust the schedule.

Starter prompt

Trial first: sort only [3] of my cron jobs and plan the move for those, written to [trial-plan.md]. Show me before you look at the rest.

Here is my list of current cron jobs and what each does: [paste list]. Sort them into three groups: real work that could run as a scheduled task from a fresh environment, jobs that only keep the system running, and jobs that need to run all day. For the first group, propose how each task reads its input from git and commits its output, and in what order they run.

This job only reads my list and writes a plan. It changes, disables or deletes nothing. Stop and wait for my yes before any job is moved or any schedule is created. A good plan is not permission. Do not ask for tokens or passwords.

Original post: Reddit · found via agentusecases.ai. Written up in our own words. We haven't run it, so test it on made-up data first.