Schedules
Run recurring work
Plenty of useful agent work has no person waiting for it. A morning digest of overnight alerts, a weekly summary of open tickets, a nightly reconciliation - all of it can run on a schedule.
Schedules in AXL are Markdown files beneath axl-config/schedules/, which means they are
reviewed, diffed, and rolled back like everything else in your configuration. There is no
separate scheduling UI holding state nobody can see.
Two modes
| Mode | Runs | Use it when |
|---|---|---|
| Task | An agent prompt | One recurring job an agent can handle in a single run |
| Workflow | A registered workflow | The recurring work is multi-step and must be durable |
A daily digest is a task. A nightly pipeline that fetches, transforms, checks, and notifies is a workflow.
How they load
The server reads and reconciles schedule files at startup, so every server instance should run the same config revision.