# Claude Code Web Scheduled Tasks > [!warning] Superseded by [[Claude Code Routines]] > On 2026-04-14 Anthropic turned these tasks into scheduled routines, which add API and GitHub triggers on top of the schedule. The docs URL below now serves the routines page, and the web UI lives at `claude.ai/code/routines`. This note keeps the original April 2026 snapshot. Cloud scheduled tasks run a prompt on a recurring cadence on Anthropic-managed infrastructure. They keep working even when your computer is off. Available to all Claude Code Web users (Pro, Max, Team, Enterprise). Use cases: daily PR reviews, overnight CI failure analysis, post-merge doc syncing, weekly dependency audits. ## Scheduling Options Comparison | | Cloud (web) | Desktop | `/loop` (CLI) | | :------------------------- | :---------- | :------ | :------------ | | 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; restored on `--resume` today) | | 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 | | Minimum interval | 1 hour | 1 minute | 1 minute | ## Creating a Task Three entry points: - **Web**: visit claude.ai/code/scheduled → "New scheduled task" - **Desktop app**: Schedule page → "New task" → "New remote task" - **CLI**: `/schedule` in any session (guided conversational setup). Also: `/schedule daily PR review at 9am` ### Configuration Steps 1. Name the task and write the prompt (self-contained since it runs autonomously). Select model 2. Add one or more GitHub repositories. Claude starts from the default branch unless prompt specifies otherwise. Creates `claude/`-prefixed branches by default; enable "Allow unrestricted branch pushes" per repo to push to any branch 3. Select a cloud environment (network access, env vars, setup script) 4. Choose schedule frequency 5. Review MCP connectors (all connected connectors included by default; remove unneeded ones) 6. Create ### Frequency Options - **Hourly**: every hour - **Daily**: once per day at specified time (default 9:00 AM local) - **Weekdays**: daily but skips Saturday/Sunday - **Weekly**: once per week on specified day/time Custom intervals (every 2 hours, first of month): pick closest preset, then update via `/schedule update` with a cron expression. Minimum interval is 1 hour. Tasks may run a few minutes after scheduled time (consistent offset). ## Managing Tasks From the task detail page: - **Run now**: trigger immediately - **Pause/resume**: toggle in the Repeats section - **Edit**: change name, prompt, schedule, repos, environment, connectors - **Delete**: removes task; past sessions remain CLI management: `/schedule list`, `/schedule update`, `/schedule run` Each run creates a new session where you can review changes, create PRs, or continue the conversation. ## References - https://code.claude.com/docs/en/web-scheduled-tasks (now serves the routines page) - Routines launch post (2026-04-14): https://claude.com/blog/introducing-routines-in-claude-code ## Related - [[Claude Code]] - [[Claude Code Routines]] - [[Claude Code Web]] - [[Claude Code Tasks]]