Set up a schedule
A schedule is a persisted task template. When the scheduled time arrives the server creates a regular task from the stored project, agent, and prompt — with the same budget checks, workspace scoping, and agent lifecycle as a manually started task.
Four cadences are available: once (a single future run), daily, weekly, and monthly.


Create a schedule
Section titled “Create a schedule”- Open Tasks in the sidebar and click Start task.
- The dialog leads with the prompt — write what the agent should do, then pick the project and agent just below it. Any secondary field (title, profile, model, effort, Git workflow, issue link) lives under the More options disclosure; you can leave it collapsed for a quick run.
- In the When segment, choose Schedule (instead of Now). This reveals the cadence controls in place — no separate toggle.
- Pick the cadence (once, daily, weekly, or monthly) and set the time or date/time.
- Click Create schedule — the task does not launch immediately; it is queued for the next due time.
To review all schedules in the workspace, open Build → Schedules.
# One-time run at a specific date and timeschedule add <project> <agent> once <YYYY-MM-DDTHH:mm> <prompt>
# Every day at a wall-clock timeschedule add <project> <agent> daily <HH:mm> <prompt>
# Every week on a given weekdayschedule add <project> <agent> weekly <weekday> <HH:mm> <prompt>
# Every month on a given day of month (1–28 or "last")schedule add <project> <agent> monthly <day-of-month> <HH:mm> <prompt>List all schedules in the current workspace:
schedules/schedule add <project> <agent> once <RFC3339> <prompt>/schedule add <project> <agent> daily <HH:MM> <prompt>/schedule add <project> <agent> weekly <weekday> <HH:MM> <prompt>For once, supply a full RFC3339 timestamp such as 2026-07-01T09:00:00Z.
Daily and weekly times are interpreted as UTC wall-clock times. Monthly
schedules must be created from the Web UI or web terminal.
List schedules:
/schedule listPause and resume a schedule
Section titled “Pause and resume a schedule”A paused schedule is retained but skipped by the background worker until it is resumed.
schedule pause <id>schedule resume <id>/schedule pause <id>/schedule resume <id>Short schedule IDs are resolved the same way as task IDs in the terminal.
Delete a schedule
Section titled “Delete a schedule”schedule delete <id>/schedule delete <id>Deleting is permanent. Pause first if you may want to reactivate later.