claude code routines are now called scheduled tasks

what a saved configuration means

a prompt is the job you want done. a repository is the project material for a code task. connectors give access to connected systems. a cloud scheduled task saves those choices together so you do not reconstruct the setup for every run.¹

for a non-developer, the first decision is whether the work belongs with a code project at all. a recurring review of project changes may fit that structure. a general household reminder may not need it. a schedule only repeats the job; it doesn't give the task anything it was missing.

where to create one, and what is limited

anthropic documents creation at claude.ai/code/routines or with /schedule in the cli. the address still contains the old name. as of 12 november 2026, availability is pro, max, ultra, team and enterprise, and the feature is a research preview.¹

the documented minimum interval for cloud tasks is one hour. the account limit is 100 scheduled runs per hour. run now, api fires and re-running one-off tasks have a 30 per hour per task limit. runs consume plan usage. those figures describe different limits, so do not read the account ceiling as permission to run a single recurring task every minute.¹

cloud tasks, local tasks and loop

• cloud scheduled tasks: run on anthropic-managed infrastructure and continue when your laptop is closed.¹
• desktop local scheduled tasks: have direct access to your machine's files and tools, but fire only while the app is open and the computer is awake.²
• /loop: repeats a prompt inside an open claude code session, with a minimum interval of one minute. the machine must stay on.³

choose the place the material lives before choosing the interval. a local folder and a cloud repository are different inputs. the laptop-closed guide explains why the location of the running program matters. a timer cannot keep a sleeping local process working.

before following a tutorial, check which one it's about: a code cloud task, a code desktop task, /loop, or a task in claude's main app.

cowork scheduled tasks are another feature to recognize

cowork and the new claude experience run saved prompts remotely, including while the computer sleeps, while tasks created before 6 october 2026 that run on the computer keep running there.⁴

see the claude scheduled tasks guide.

dusk routines start with a message

in dusk bot, a routine is a job a bot does without being asked again. tell it the job and timing in plain words. the bot returns a card showing the schedule and next runs, with Edit, Pause and Undo. Automations lists routines with a calendar and run history.⁵

a routine can also start from an event in a connected app. on your own computer, nothing runs while it sleeps or dusk bot is closed. a run missed by less than 12 hours runs once when you return; older missed runs are skipped. dusk cloud runs them on time. scheduled ai tasks helps compare what you need to keep awake.⁵

review the result before making it recurring

write a narrow job with its input, destination and reason to stay quiet. try the underlying task once and check its sources. if the result is missing context, fix that before adding a schedule.

in dusk bot, read-only app access is the strongest starting boundary for a reading routine. if you later allow app changes, include "ask me before you change anything" when you want them supervised. sends have their own approval rule, unless you choose a daily amount. one exception: a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so set Ask every time for it.⁷ don't give a routine more access just because it runs on its own.⁶