Skip to content
#0101
Daemon

A 6-hour data backfill you can close the laptop on

You need to backfill three years of analytics rows into a new schema. The job runs six hours. Running it in a terminal means the laptop stays open. Running it as a cron is the wrong primitive: it's not recurring. Spinning up a Lambda or a Cloud Run job is more YAML than the job itself.

You POST to /api/v1/daemon/quick-start with the backfill command and ttl: 25200 (seven hours, one of buffer). It launches as an ephemeral program: managed, supervised, log-captured, but not saved to permanent config. You close the laptop.

Six hours later you GET /quick-start/{id}/status from your phone: STOPPED, exited cleanly. You GET the logs URL, see the row count. You don't have to clean anything up: the ephemeral config self-deletes.

Long jobs used to require a screen session. Now they require one POST and a closed laptop.