Blog · · Dimitris Kyriakakis

Claude Code scheduled tasks explained: /loop, Desktop and cloud

Claude Code can repeat work on a timer: poll a deploy, review open PRs every morning, or have a session check a build later. Anthropic ships three schedulers for this. They are easy to mix up, and only two of them depend on your Mac.

The three schedulers

Cloud scheduled tasks (formerly routines) run on Anthropic's machines. Create them at claude.ai/code/routines, from Claude Desktop, or with /schedule in the CLI (/routines is an alias). They need a Pro, Max, Ultra, Team or Enterprise plan.

Desktop scheduled tasks run on your Mac. In Claude Desktop, turn on Only on this computer when you create the task and pick a local folder. Desktop asks you to trust the folder if you haven't yet.

**/loop** runs inside an open CLI session. /loop 5m check the deploy repeats the prompt every five minutes while that session is open and idle. A recurring loop expires after seven days.

They also differ on permissions. A cloud run starts in auto mode and stops to ask only when a rule says ask or after repeated blocks. A Desktop task has a permission mode you set per task; in Manual mode, a run waits until you approve. /loop uses the session's own permissions.

Anthropic's docs have the full detail: Automate work with scheduled tasks, Run prompts on a schedule and Schedule recurring tasks in Claude Code Desktop.

What stops a local run

A Desktop task and a /loop job are both processes on your Mac.

  • A Desktop task runs only while the app is open and the Mac is awake. If the Mac sleeps through the scheduled time, that run is skipped. When the Mac wakes, Desktop starts one catch-up run for the most recent missed time in the last seven days and drops the older ones.
  • A /loop job has no catch-up. It fires only while Claude Code is running and idle.
  • A run that hits a permission prompt waits until someone answers it.

Claude Desktop has a Keep computer awake setting for its tasks. Closing the lid still puts the Mac to sleep.

What AgentNod shows

AgentNod's Scheduled runs section lists the Desktop tasks on your Mac:

  • Each task with its name, its folder and how often it runs, in words such as "daily at 09:17", taken from the schedule the Claude app keeps. A paused task says so.
  • The last run's outcome from the Claude app's own summary, and when the next run is due.
  • Every run, one click from opening it in the Claude app, plus a live line while a run is going.

Task definitions come from ~/.claude/scheduled-tasks/, and schedules and runs from the Claude app's own records on your Mac. Nothing is fetched from a server. Cloud tasks that never run on this Mac aren't in the list, and neither are /loop jobs. A loop's prompts still reach AgentNod, through the session it runs in.

When a scheduled run stops to ask for permission, it joins the same queue as any other session, so you can answer from the HUD or from your phone. Night watch keeps the Mac awake while a scheduled run is going and lets it sleep when nothing is left.