Schedule

Scheduling lets you run Syntic Code prompts automatically on a recurring basis, without anyone starting a session. This is ideal for routine maintenance that benefits from an agent’s judgment: triaging new issues each morning, sweeping for outdated dependencies weekly, or summarizing overnight CI results. A schedule pairs a cron expression with a prompt and runs it in headless mode.

Creating a schedule

Schedules are defined with the syntic schedule command. You provide a name, a cron expression, and the prompt to run. The prompt executes in the repository’s working directory with the same tools and permissions as an interactive session:

# Every weekday at 9am, triage newly opened issues
syntic schedule create \
  --name morning-triage \
  --cron "0 9 * * 1-5" \
  --prompt "Review issues opened since yesterday, label them, and post a summary."

Managing scheduled runs

You can list, inspect, pause, and remove schedules at any time. Each run is recorded so you can review what Amara did and how it exited:

syntic schedule list                 # show all schedules
syntic schedule runs morning-triage  # show past runs for one schedule
syntic schedule pause morning-triage # temporarily disable
syntic schedule remove morning-triage

Execution model

Scheduled runs are non-interactive: Amara cannot ask you a clarifying question mid-run, so write prompts that are self-contained and specify what to do when information is missing. Each run starts from a clean session unless you attach it to a goal for continuity. Output and exit codes follow the same conventions as programmatic usage, which makes it easy to forward results to a chat channel, an email, or a dashboard. Combine schedules with hooks to enforce policy on what automated runs are permitted to change.