Scheduled task
A recurring or one-off agent invocation, fired by time rather than by user message. Cron-style ('every weekday at 7am'), interval ('every 4 hours'), one-shot ('Friday at 6pm'), or ISO timestamp.
Why it matters
The original "computers can do this for you" feature is the scheduled job. Cron has been around since 1975. The friction has always been the syntax: cron expressions, recurring-event rules, alarm presets. A scheduled task in a personal AI agent removes the syntax: the user describes the schedule in plain English, the agent translates internally.
A scheduled task fires as a full agent invocation. It is not a static notification. The agent has access to its tools, its memory, and its skills when the task fires; the morning brief is itself a scheduled task that pulls calendar, inbox, and tasks fresh on each fire.
How Ajeris handles this
Scheduled tasks are stored in UTC with the user's local time as a secondary field. The heartbeat scheduler ticks every 60 seconds and fires due tasks. Tasks can be paused, resumed, patched, or triggered immediately. The task itself is a description in natural language; the agent decides what tools to call when the task fires.
