Run agents on a schedule

A cron trigger runs an agent on a schedule. Ellipsis registers the schedule when the config syncs from your default branch, and each fire starts a fresh run with the agent's system as its instruction. There is no typed prompt.

A daily triage agent for Splitshift's API team:

ellipsis:
  version: v1
  name: Daily issue triage
  description: Triages new issues every weekday morning

claude:
  system: |
    Find open GitHub issues in splitshift-api that need attention.
    Prioritize bugs in shift trading and schedule assignment, stale
    customer reports, and blocked pull requests. Post a concise
    triage summary as a comment on each issue you touch.

triggers:
  - type: cron
    schedule: "0 14 * * 1-5"

sandbox:
  repositories:
    - name: splitshift-api

limits:
  run: 1.00
  day: 2.00

Each weekday at 14:00 UTC this produces a run whose summary reads like:

Triaged 6 issues. Flagged #431 (trade requests stuck in pending
when the counterparty account is deactivated) as the priority:
likely regression from #418. Labeled 3 as needs-repro, closed 2
duplicates of #405.

Schedule syntax

schedule takes a standard five-field cron expression: minute hour day-of-month month day-of-week. All schedules run in UTC.

You cannot restrict both day-of-month and day-of-week in the same expression; leave one as *.

Ellipsis also accepts AWS EventBridge Scheduler expressions verbatim: cron(...), rate(...), or at(...).

triggers:
  - type: cron
    schedule: "rate(6 hours)"

Multiple schedules

A config can declare several cron triggers; each fires independently. Editing or removing a trigger updates the schedule on the next sync, and an invalid cron expression fails validation before anything is stored.

Next

Cap what scheduled runs can spend with budgets, or mix a cron trigger with react triggers in the same agent.