Schedule tasks on the web

• Reviewing open pull requests each morning
• Analyzing CI failures overnight and surfacing summaries
• Syncing documentation after PRs merge
• Running dependency audits every week

Compare scheduling options

Claude Code offers three ways to schedule recurring work:| Cloud | Desktop | /loop | | |---|---|---|---| | Runs on | Anthropic cloud | Your machine | Your machine | | Requires machine on | No | Yes | Yes | | Requires open session | No | No | Yes | | Persistent across restarts | Yes | Yes | No (session-scoped) | | 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 |

Create a scheduled task

You can create a scheduled task from three places:Web: visit claude.ai/code/scheduled and clickNew scheduled task****Desktop app: open theSchedulepage, clickNew task, and chooseNew remote task. See Desktop scheduled tasks for details.CLI: run/schedule

in any session. Claude walks you through the setup conversationally. You can also pass a description directly, like/schedule daily PR review at 9am

.

Name the task and write the prompt

Give the task a descriptive name and write the prompt Claude runs each time. The prompt is the most important part: the task runs autonomously, so the prompt must be self-contained and explicit about what to do and what success looks like.The prompt input includes a model selector. Claude uses this model for each run of the task.

Select repositories

Add one or more GitHub repositories for Claude to work in. Each repository is cloned at the start of a run, starting from the default branch. Claude creates

claude/

-prefixed branches for its changes. To allow pushes to any branch, enable Allow unrestricted branch pushesfor that repository.Select an environment

Select a cloud environment for the task. Environments control what the cloud session has access to:

Network access: set the level of internet access available during each runEnvironment variables: provide API keys, tokens, or other secrets Claude can useSetup script: run install commands before each session starts, like installing dependencies or configuring tools

Defaultenvironment is available out of