Schedules let an agent keep working after the immediate thread is done. They are part of the same harness as normal agent work: the runtime owns the durable state, recovers from transient failures, and gives the scheduled work the agent’s configured context and tools. Enable theDocumentation Index
Fetch the complete documentation index at: https://docs.cerca.dev/llms.txt
Use this file to discover all available pages before exploring further.
agent.schedule.* namespace when the agent should be able to create or manage scheduled work from inside a thread. Keep the instructions specific: what should happen, when it should happen, and what approval gates apply if the scheduled task needs to take action.
Use schedules for jobs that belong with the agent’s long-lived responsibility, such as checking a queue, preparing a recurring report, or following up later. Do not use them as a replacement for your product’s own source of truth. Your app should still store the business record; the agent should store the work plan and execution context.
When a schedule fires, the runtime emits a schedule.triggered webhook so your product can observe the run without polling.