[Cloud sessions] Offset default routine schedules
CHANGELOG · original
[Cloud sessions] Changed new routine schedules to default to a few minutes past the hour, with a note that routines set exactly on the hour can start several minutes late Open official changelog ↗ Documentation
Documentation excerpt
Add a schedule trigger
A schedule trigger runs the task on a recurring cadence, or once at a specific future time. In the task's creation or edit dialog on the web, pick a preset frequency such as hourly, daily, or weekly:
- Runs on the hour: if you schedule a run exactly on the hour, such as 9:00, it can start several minutes late. To start close to the scheduled time, pick a few minutes past the hour, for example 9:07.
- Custom intervals: for a cadence the presets lack, create the task and select Custom in its edit dialog. Then enter a cron expression, such as
0 */2 * * *for every two hours. To set one from the CLI, run/schedule update. Expressions that run more often than once per hour are rejected. - Time zone: when you pick a preset frequency, enter the time in your local time zone.
- Cron expression time zone: when the expression is five fields alone, write the hours in UTC, so
0 9 * * 1-5runs at 9:00 AM UTC on weekdays. If the field opens with aCRON_TZ=prefix, keep it and write the hours in its zone, or delete it and write them in UTC.
Schedule a one-off run
A one-off schedule runs the task a single time at a specific timestamp. For example, use it to:
- Remind yourself later in the week
- Open a cleanup PR after a rollout finishes
- Start follow-up work after an upstream change ships
After the task runs, it turns itself off and the web UI marks it as Completed. To run it again, open the task's edit dialog on the web and select One-time or Once, whichever label your dialog shows. Then set a new date and time in your local time zone and save.
Create a one-off run from the CLI by describing the time in natural language. Claude resolves the phrase against the current time and confirms the absolute timestamp before saving.
/schedule tomorrow at 9am, summarize yesterday's merged PRs
/schedule in 2 weeks, open a cleanup PR that removes the feature flag
One-off runs count against the same hourly limit as other scheduled runs. See Usage and limits for details.
Documentation snapshot · 2026-11-20