Claude Code Cloud Schedule: Runs With Your Laptop Off

The Stack

Tested Against

Steps

1. 1

   Create the cloud schedule

   Create one at claude.ai/code/routines or with /schedule in the CLI. The minimum interval is 1 hour, and each run can only push to claude/-prefixed branches by default, so a bad run cannot touch main.

2. 2

   What CI checks: the interval is 1-hour-or-coarser and the branch restriction is kept

   CI rejects a sub-hourly expression like */30 * * * * (a single-integer minute fires at most hourly; a wildcard or step minute fires sub-hourly) and confirms the config keeps the default claude/ branch prefix. No model runs.

   cat > cloudcron.mjs <<'EOF'
   // Cloud routines require >= 1 hour granularity: a single-integer minute fires at
   // most hourly; '*' or '*/n' or lists fire sub-hourly and are rejected.
   function granularityOK(expr){
     const f = expr.trim().split(' ').filter(Boolean);
     if (f.length !== 5) return false;
     const minute = f[0];
     return minute.length > 0 && [...minute].every(c => c >= '0' && c <= '9');
   }
   if(!granularityOK('0 9 * * 1-5')){ console.log('FAIL valid rejected'); process.exit(1); }
   console.log('VALID (>=1h): 0 9 * * 1-5');
   if(granularityOK('*/30 * * * *')){ console.log('FAIL sub-hourly accepted'); process.exit(1); }
   console.log('REJECTED (sub-hourly): */30 * * * *');
   const config = { branchPrefix: 'claude/' };
   if(config.branchPrefix !== 'claude/'){ console.log('FAIL branch restriction'); process.exit(1); }
   console.log('branch restriction kept: ' + config.branchPrefix);
   console.log('cloud schedule check OK');
   EOF
   node cloudcron.mjs

3. 3

   Let the cloud run it (the model step, not checked by CI)

   The scheduled run is fully autonomous on Anthropic infra. That run invokes the model and is non-deterministic, so it is fenced: CI verifies the cadence and the branch safety, never the run's output.