The best work an agent does is the work you never asked for, because it was already on the calendar. Scheduling is how your system stops waiting for you and starts running on its own, so you wake up to work that is already done.
3.9.1Agents that run without you
Until now, every agent waited for you to press go. Scheduling flips that. You put an agent on a clock and it runs on its own, on time, whether or not you show up.
That is the moment the system stops being a tool you operate and starts being one that operates, doing the rounds because the clock struck, not because you remembered.
3.9.2Put the routine work on a clock
Look at everything you do on a rhythm: the weekly numbers, the daily health check, the monthly money review. Every one is a scheduled agent waiting to exist.
You set its cadence with a cron line, five fields that mean "run at this time":
# min hour day month weekday
0 8 * * * # every day at 08:00
0 9 * * 1 # every Monday at 09:00
Write the job once, give it a cadence, and it runs forever. The work that is important but never urgent, and so never gets done, finally does, because a clock does not procrastinate.
That format is cron, which is built into Mac and Linux. Windows has the same thing under a different name, Task Scheduler. You do not set either up by hand: you tell your agent the cadence and let it wire the right one for your machine.
3.9.3Schedule it, or trigger it on demand
The same job has two doors. On a schedule, it runs every morning at eight. On demand, you run one command and it goes now. You want both: the schedule for the rhythm, the manual run for the moment you need the report early.
A plain cron runs this on your machine; a job runner handles it at scale when you have many. Same idea, bigger engine.
3.9.4Make an unattended run safe
A job that runs while you sleep needs more than a clock, or it fails in the dark and you find out late. Three things make an unattended run trustworthy:
- Gate: before it acts, the agent confirms it is still allowed to (the guardrails of the next chapter). It fixes what is safe and escalates the rest, never spending or deleting on its own.
- Record: every run writes what it did to one log (you build this in the ledger chapter), so "what ran last night" has one honest answer.
- Watchdog: something alerts you when a run stops firing. A scheduler does not fail loudly; it goes quiet, so you alert on the missing run, not just on errors.
3.9.5Wake up to finished work
This is the payoff, and it changes how the whole thing feels. You open your laptop and the reports are already written, the checks already run, the problems already flagged or fixed.
You are not starting the day's work. You are reviewing work that already happened. The system ran a full shift while you slept.
3.9.6Put one job on a clock
This prompt turns a routine chore into a scheduled agent:
Act as a senior engineer automating my routine work. Take
the one task I describe below, write it as a small job my
agent can run on its own, and schedule it at the right
cadence using whatever my operating system provides (cron on
Mac or Linux, Task Scheduler on Windows). Show me how to run
it once by hand to test it first.
My operating system and the routine task (and how often):
Do this now: paste the prompt, pick one thing you do on a rhythm, and let your agent turn it into a job on a clock.
