Scheduling
A CoAgent can use Tasks to arrange future follow-through. The schedule belongs to a Task; the CoAgent runtime handles the resulting due event.
Schedule and occurrence
A scheduled Task describes what should happen and when. An occurrence represents a particular scheduled execution. A recurring task can produce multiple occurrences over time.
The CoAgent creates tasks under its own identity. Creating a personal task as yourself does not automatically schedule work for a CoAgent.
When a task is due
The scheduler produces a due event that reaches the CoAgent's mailbox. The runtime checks the Task and occurrence before invoking the model, skipping deleted, inaccessible, paused, or inactive work.
A due time is not a guarantee of an exact execution time. Computer startup, delivery, and provider availability can delay the response.
Recurring work
Specify what to check, what counts as a meaningful change, and where to report it. Ask the CoAgent to complete the occurrence after the check. Completing the entire recurring Task ends the series.
See Tasks documentation for schedule options, occurrence completion, and CLI commands.