agints.
← warehouse
Keep · cron SKILL.md

Claude Code cron: /loop, CronCreate, Desktop tasks, cloud Routines

WhenUse when a skill is trusted and the next question is which scheduler owns cadence.
StopNever schedule a skill that has not been run once. Never let cloud routines touch unstated local files.

Steps

  1. Three layers of scheduling.
  2. Also: https://code.claude.com/docs/en/desktop-scheduled-tasks and https://code.claude.com/docs/en/routines
  3. | | Cloud (Routines) | Desktop scheduled tasks | /loop | | --- | --- | --- | --- | | Runs on | Cloud, Anthropic-managed by default | Your machine | Your machine | | Requires machine on | No | Yes | Yes | | Requires open session | No | No | Yes | | Persistent across restarts | Yes | Yes | Restored on --resume if unexpired | | Access to local files | No (fresh clone) | Yes | Yes | | MCP servers | Connectors configured per task | Config files and connectors | Inherits from session | | Permission prompts | No (runs autonomously) | Configurable per task | Inherits from session | | Customizable schedule | Via /schedule in the CLI | Yes | Yes | | Minimum interval | 1 hour | 1 minute | 1 minute |
  4. Use cloud for work that must run with the laptop closed.
  5. Session-scoped /loop and CronCreate live in the current conversation and stop on a new one.
  6. | What you provide | Example | What happens | | --- | --- | --- | | Interval and prompt | /loop 5m check the deploy | Prompt runs on a fixed schedule | | Prompt only | /loop check the deploy | Claude chooses delay each iteration (1m–1h) | | Interval only, or nothing | /loop or /loop 15m | Built-in maintenance prompt, or your loop.md |
LoadClaude Code /loop, CronCreate, or cloud Routines. Skill first.
Copy SKILL.mdRaw SKILL.md
---
name: Claude Code cron: /loop, CronCreate, Desktop tasks, cloud Routines
description: Use when a skill is trusted and the next question is which scheduler owns cadence.
---

# Claude Code cron: /loop, CronCreate, Desktop tasks, cloud Routines

When: Use when a skill is trusted and the next question is which scheduler owns cadence.
Stop: Never schedule a skill that has not been run once. Never let cloud routines touch unstated local files.

1. Three layers of scheduling.
2. Also: https://code.claude.com/docs/en/desktop-scheduled-tasks and https://code.claude.com/docs/en/routines
3. | | Cloud (Routines) | Desktop scheduled tasks | /loop | | --- | --- | --- | --- | | Runs on | Cloud, Anthropic-managed by default | Your machine | Your machine | | Requires machine on | No | Yes | Yes | | Requires open session | No | No | Yes | | Persistent across restarts | Yes | Yes | Restored on --resume if unexpired | | Access to local files | No (fresh clone) | Yes | Yes | | MCP servers | Connectors configured per task | Config files and connectors | Inherits from session | | Permission prompts | No (runs autonomously) | Configurable per task | Inherits from session | | Customizable schedule | Via /schedule in the CLI | Yes | Yes | | Minimum interval | 1 hour | 1 minute | 1 minute |
4. Use cloud for work that must run with the laptop closed.
5. Session-scoped /loop and CronCreate live in the current conversation and stop on a new one.
6. | What you provide | Example | What happens | | --- | --- | --- | | Interval and prompt | /loop 5m check the deploy | Prompt runs on a fixed schedule | | Prompt only | /loop check the deploy | Claude chooses delay each iteration (1m–1h) | | Interval only, or nothing | /loop or /loop 15m | Built-in maintenance prompt, or your loop.md |

Load: Claude Code /loop, CronCreate, or cloud Routines. Skill first.

Get my agents setup

your agents work while you sleep.