Schedules
Use schedules when you want recurring local jobs such as nightly compile runs, weekly lint sweeps, or scheduled query/explore jobs that stage new output pages for review.
Example
{
"schedules": {
"nightly-compile": {
"enabled": true,
"when": { "cron": "0 3 * * *" },
"task": { "type": "compile", "approve": true }
},
"weekly-report": {
"enabled": true,
"when": { "every": "7d" },
"task": {
"type": "query",
"question": "Summarize the latest vault changes as a report",
"format": "report"
}
}
}
}Trigger Shapes
when.cron- Five-field UTC cron expressionwhen.every- Simple interval such as15m,2h, or1d
Task Shapes
compilewith optionalapprovelintwith optionaldeepandwebquerywithquestion, optionalformat, and optionalsaveexplorewithquestion, optionalsteps, and optionalformat
Behavior
- Disabled jobs stay in config but do not run
- Scheduler state is stored in
state/schedules/ - Schedule runs are serialized at the vault level
- Scheduled
queryandexplorejobs stage outputs into approvals when they save