Schedules

AI agents: read the complete documentation index. Append .md to any docs URL for its Markdown version.

A schedule authorizes a defined task to run at a future time or on a repeating cadence. Request and manage schedules through project chat. Scheduled work runs through the relay and the agent on your computer, just like a milestone.

Before you schedule work

Set up the relay and a ready agent. Name the deliverable, definition of done, time zone and cadence. Keep the computer awake and relay online when the work is due. Provider usage and Chief plan limits still apply.

Creating a schedule is authorization for its future runs: you do not approve each occurrence with Go. This is separate from auto mode, which evaluates Chief's own proposals.

Create a schedule in chat

Send a precise request, for example:

Every Monday at 09:00 America/New_York, review this project's README
for outdated local setup instructions. Produce a short report with file
references; do not edit files or deploy anything. Done means the report
lists each mismatch or says that none were found. Call this schedule
"Weekly setup review".

For a one-off task, specify an actual future date and time. You can also ask for interval-based work. If the request or time zone is ambiguous, answer Chief's clarification before assuming anything was scheduled.

Chief saves a valid schedule from chat and appends a confirmation naming the schedule, resolved cadence and upcoming run times. It does not require a separate draft-approval step.

Expected result: the reply includes Scheduled and the next run or runs. Read that confirmation rather than relying only on the conversational reply. If Chief says it could not schedule the work, resolve the stated problem and try again.

Check the time zone

Include an explicit zone such as America/New_York or Europe/Berlin to avoid ambiguous abbreviations. Without an explicit zone, Chief uses the browser's time zone when available, otherwise your profile's zone. If the browser and profile disagree, the confirmation explains the difference. Tell Chief which zone to use if it chose the wrong one.

Calendar recurrences follow the schedule's local time zone through daylight-saving changes. Always inspect the upcoming dates and times, especially around clock changes.

Change or cancel through chat

Name the schedule clearly when asking for a change:

Move "Weekly setup review" to Tuesdays at 10:00 America/New_York.
Keep its task and definition of done the same.

An edit retains the schedule's time zone unless you specify another. You may request a different agent by name; otherwise the schedule uses the project's default. Verify the resulting confirmation and upcoming runs.

To stop future occurrences:

Cancel the schedule "Weekly setup review".

Expected result: Chief confirms cancellation and says nothing more will run from that schedule. Cancellation stops future runs; inspect any already-running milestone separately.

Follow runs and recover

Scheduled occurrences create milestones. Read their progress and result in Tasks and History; a task can identify its originating schedule. Chief posts chat notices for failures, plan limits and automatic pauses.

An offline relay can delay a run within its permitted lateness window. Missed occurrences do not accumulate into unlimited catch-up work, and a run can be skipped if the previous occurrence is still active. Repeated failures or plan-limit skips can pause the schedule. Read the notice and fix the underlying cause; a chat edit to its time does not resume an already-paused schedule. Contact Support if you need help restoring it.

Follow relay recovery or failed-task recovery as appropriate. If Chief reports scheduled tasks are paused for maintenance, wait for service restoration before creating or restarting scheduled work.