Overview
A scheduled task can be created through a guided conversation or entered manually. Its configuration includes:
- A name.
- The requirement describing what the agent should do.
- A frequency, such as daily, weekly, monthly, or one time.
- An execution time.
- An expiration condition, when the automation should stop after a defined period.
Once scheduled, the task runs as a recurring loop. A job identifier and schedule make the automation visible, and the job can be canceled.
Execution location is critical.
A desktop task depends on the local desktop environment being available. If the computer will not remain open, a task intended to run during the night should be placed in a cloud environment instead. The cloud job can continue independently and be checked later.
Scheduled work also changes the importance of latency. A reasoning model may be slow in an interactive session, but that delay is less disruptive when the task runs unattended and the user reviews the result later.