Schedule
The Schedule page manages one-time and recurring task execution for the selected project. Scheduled work is intentionally handled outside normal task category selection so users can reason about time-based automation separately from the task board.
What Users Do
Open Schedule from the Workspace section of the sidebar.
| UI Action | Product Effect |
|---|---|
| Create a schedule | Picks a task and a time for it to run. |
| Choose recurrence | Runs the task once or repeats it at an interval. |
| Enable or disable | Controls whether future runs should happen. |
| Reschedule | Changes when the task should run next. Select several schedules with Command-click on macOS or Ctrl-click on other systems, then drag one selected schedule to move all selected schedules together while preserving their relative time offsets. |
| Delete schedule | Removes the future automation without deleting the underlying task. Deleting a scheduled task from task detail returns to Schedule. |
Repeat Types
| Repeat Type | Use It For |
|---|---|
| Once | A single future run. |
| Seconds | High-frequency testing or development-only loops. |
| Minutes | Short operational intervals. |
| Hours | Repeated maintenance throughout a day. |
| Daily | Daily checks or recurring implementation tasks. |
| Weekly | Weekly cleanup, reporting, or backlog review. |
| Monthly | Long-running maintenance cadence. |
Move Several Schedules
Use Command-click on macOS or Ctrl-click on other systems to select multiple schedule cards. Drag any selected card to a new time to move every selected schedule by the same offset, preserving their relative spacing. The action can reschedule disabled entries too; selecting them does not enable future dispatch.
Schedule Or Automation
Use Schedule when one task needs to run once or repeat. Use Automations when timed work must hand off to additional tasks, Native human approvals, supported GitHub actions, or explicit outcomes. A Schedule node in an Automation creates its own task and schedule when the graph is saved.
How Schedule Relates To Tasks
A schedule belongs to a task. The task defines the prompt, model, agent, attachments, repository context, and review behavior. The schedule only controls when and how often that task should run.
Use the task board for immediate work. Use Schedule when the timing matters.
Related Pages
| Page | Why It Matters |
|---|---|
| Automations | Connect scheduled work to tasks, approvals, GitHub actions, and outcomes. |
| Tasks | Scheduled work runs existing task definitions. |
| Scheduled Task Runs | Deeper automation guidance for recurring work. |
| Alerts | Failed scheduled runs can create alerts. |
| Memory | Some schedule-adjacent controls may surface project memory behavior. |