Work
Schedules and monitors
Work that starts without you — on a clock, or when a condition changes.
Schedules and monitors are how work starts while you’re doing something else. Both produce ordinary tasks — visible in Tasks, inspectable in the Cockpit, pausing for approval exactly like work you started by hand.
Schedules — on a clock
Section titled “Schedules — on a clock”Attach a schedule to a Routine or a described task: every weekday at 8:00, every Monday, the first of the month. The run happens whether or not you’re online; anything needing your judgment waits in a pause until you appear.
Monitors — on a condition
Section titled “Monitors — on a condition”A monitor watches for a state change and acts when it happens: a table record hits a threshold, an expected email arrives, a check fails. When the condition fires, the monitor’s task runs — same session, same controls.
The morning-after habit
Section titled “The morning-after habit”Scheduled work leaves you a review surface, not a mystery: open Tasks, see what ran overnight, what finished, and what’s waiting on you. Paused runs tell you exactly which of the three states they’re in — approval, input, or authentication.
Failure and recovery
Section titled “Failure and recovery”- A scheduled run failed → the session shows the failing step; fix the cause (an expired credential, a changed site) and re-run.
- Too noisy → tune the routine’s constraints or the monitor’s condition; the goal is runs you’d approve, not runs that page you.
- A run is waiting every single time → that pause is telling you something; either vault the credential, answer the recurring input into memory, or accept that this task genuinely needs you each run.