11 cron jobs, the server is not switched off

What was done

On 24 March 2026 u/jonathanmalkin writes in r/ClaudeCode that scheduled tasks in Claude Code Cloud made him ask if the VPS can be switched off. For the past six months he has run Claude Code in three environments, with 11 cron jobs. A Slack daemon runs 24/7, so he can write to Claude from his phone with project context. Nightly runs make retrospectives and morning notes. There is also a content schedule and email. The code is at github.com/jonathanmalkin/jules. He spent more time keeping the automation up than using it, with auth failures at 2 at night. The tweet scheduler reads a queue in git and posts through the X API. The email run uses IMAP. He counted that 7 of the 11 cron jobs only keep the system running. The cloud tasks could take some of this, but each run is a new environment. Slack has to listen all the time. The cloud service cannot. He has not switched the VPS off.

How it went

The system on the VPS is the one that runs, with posting and email as he describes it. The move to the cloud is not done. 7 of 11 jobs are the ones he says only keep the machinery up.

Worth knowing

A count of tweets and emails is not given. 2 at night is the example of auth failure, not a count of failures. The post does not say the VPS was switched off later.

How to do it

1. List the cron jobs and mark the ones that do the work, and the ones that only keep the system up.
2. Leave a listener, such as Slack, where it has to stay on.
3. Do not post, do not send email and do not switch off the server before you have said yes.