Schedules

A schedule runs a brief on a repetition. Every run is kept, and every result lands in one place you can read later.

You do not fill in a cron expression. You ask for it in chat, or you open Schedules and describe what should happen and when.

What a schedule can be about

A schedule stands on one of three subjects, and the subject decides where its results go.

• On its own. A standing brief with no other object attached. "Every weekday at nine, summarise what changed in the repository since yesterday." Results collect in the schedule's own history.
• A task card. The card is re-run on the repetition, and every result is collected on that card. This is how a recurring check becomes part of the board rather than a separate stream you have to remember to read.
• A design. Each run lands on that design's plane, so a recurring brief can keep producing work into the same canvas. The design shows that it is fed by a schedule, so nobody wonders where the new frames came from.

Every run is a conversation

A scheduled run is not a log line. It streams into a real conversation you can open, read and continue, exactly like a session you started yourself. That is the difference between a job that ran and work you can inspect.

It refuses to start work it cannot finish

Agents run against a quota that resets on a clock. A scheduled task that starts with thirty minutes of headroom and needs two hours does not produce a useful result, it produces a truncated one.

So before a run starts, a quota gate compares the headroom you have left against the reset time and what this task has historically needed. If it clearly will not fit, the run is deferred to the reset and you are told, rather than being quietly downgraded to a weaker engine to squeeze it in.

A task that has never run before is not deferred. It runs untimed the first time, because the honest thing to do with an unknown is measure it.

On every surface

Schedules are not a desktop feature with a mobile viewer. They exist as their own surface in Studio, in the browser, and in the iOS app, because the moment you most want to check whether last night's run produced anything is rarely the moment you are at your desk.

See Pathrule for iOS for what the phone can do with them.