Schedules

Schedule AI coding tasks in plain English or cron.

Tell your AI coding assistant when, in plain words or cron. It comes back on its own, in the same project and with everything it already knows, and posts what it finds.

Plain words in, schedule out

Say when. It works out the rest.

Pick an example to see how a plain-words request becomes a schedule, and how the three kinds of run look in the Schedules pane.

New schedule
Every weekday at 9, check yesterday’s bookings and flag anything odd
WhenWeekdays · 09:00
Next runNext weekday, 09:00
Runs inBookings app
Check overnight bookings and flag anything oddWeekdays · 09:00 · set by youAlways
Check the deploy againIn 5 minutes · set by the agent while it waitsThis window
Draft the weekly summaryMondays 08:30 · app was closed · last ran 10:12, lateRan late
Examples

Recurring work, by the kind of person doing it.

For developers

Every weekday at 9, check yesterday’s failing builds. Check the deploy again in 5 minutes. Look for new dependency warnings on Mondays.

For product people

Every Monday at 8:30, draft the weekly summary of what shipped. Each morning, flag anything odd in yesterday’s bookings.

For someone with one project

Remind me on Friday to review this week’s changes. Check back tomorrow and tell me whether the tests still pass.

Built to be trusted

Honest about when it runs, and when it did not.

Right time all year

Schedules follow your local time, so a 9:00 run stays at 9:00 when the clocks change.

Always or this window

Always schedules survive a restart. This window follow-ups end when you close it, and the app says which is which.

Nothing silently missed

If the app was closed, the run happens once on launch and is marked late, so you know it did not run on time.

The agent can set its own follow-ups while it waits on something slow. Those are marked Agent in the list, next to the ones you created.

Part of the loop

Schedules work with plans and skills.

A scheduled run happens in the same project, so it starts with the same context as any other task and reports back in the same place.

Read about plans and reports or skills for your AI coding agent.

Questions

Scheduling AI coding tasks, answered.

Can I use cron?

Yes. Describe the timing in plain words, such as every weekday at 9, or write a cron expression if you prefer. Both end up as the same schedule.

What is the difference between This window and Always?

An Always schedule survives restarting the app. A This window schedule is a follow-up that ends when you close the window, and it says so when it is created.

What if the app is closed when a run is due?

The run happens once when the app launches and is marked as late, so you can see it was not on time. Nothing is silently skipped.

Do schedules follow daylight saving time?

Yes. A schedule for 9:00 stays at 9:00 local time when the clocks change.

Can the AI schedule its own follow-ups?

Yes. While waiting on something slow, such as a deploy, it can schedule a check and come back. Those schedules are marked Agent so you can tell them apart from yours.

Keep exploring

How it works

Follow one idea through the researcher, product manager, designer, engineer and QA.

See the whole loop →

Plans and reports

Reports you can sort and question, and plans split into reviewable steps.

Explore plans and reports →

Skills

Reusable playbooks in your project that your AI coding agent follows.

See skills →
Start

Start with one idea.

Describe something you have been putting off. Read the plan, approve the screens, and decide whether to let it build.

macOS 12+ · Windows 10+ · Ubuntu 20.04+  ·  See what shipped in 2.8.0