Claude Code Introduces Web-Based Scheduled Tasks for Automation

If you're a developer who relies on automation to streamline your workflow, Claude Code's new web-based scheduled tasks might be just what you need. This feature allows you to run prompts at regular intervals using Anthropic-managed cloud infrastructure, ensuring that your tasks continue to execute even when your computer is offline.

What Changed and Why It Matters

Previously, scheduling tasks with Claude Code required keeping your machine running or using the /loop command within a session. Now, with web-based scheduled tasks, you can automate recurring work without worrying about your local environment. This is particularly useful for:

• Reviewing open pull requests each morning
• Analyzing CI failures overnight and summarizing results
• Syncing documentation after PRs merge
• Running dependency audits weekly

These tasks are available to all Claude Code on the web users, including Pro, Max, Team, and Enterprise plans.

Compare Scheduling Options

To help you decide which scheduling method fits your needs, here’s a breakdown of the three options:

| | Cloud (Web) | 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 | [Conf] |

Creating a Scheduled Task

To set up a scheduled task, follow these steps:

1. Navigate to the Claude Code web interface and go to the "Scheduled Tasks" section.
2. Click on "Create Task" and select the repository and branch you want to use.
3. Define the frequency of the task (e.g., daily, weekly).
4. Write your prompt or select a pre-defined one from the library.
5. Save and confirm the task details.

Frequency Options

You can set tasks to run at various frequencies:

• Daily: Every 24 hours
• Weekly: Once per week
• Custom: Define a specific cron-like schedule for more granular control

Repositories and Branch Permissions

When creating a scheduled task, you need to specify the repository and branch. The task will have access to the code in that branch, but it won't be able to write changes back to the repository unless explicitly configured.

• Read-only access: By default, tasks can only read from the specified branch.
• Write access: If you need to make changes, configure the task with the necessary permissions.

Connectors

Connectors are pre-configured integrations that allow your scheduled tasks to interact with other services. For example:

• GitHub: Pull data from repositories
• Jira: Create or update issues
• Slack: Send notifications

Each connector can be configured per task, ensuring that you have the right level of access and functionality.

Environments

You can run scheduled tasks in different environments to match your development, staging, and production workflows. This helps ensure that changes are tested and validated before they reach production.

• Development: For testing and experimentation
• Staging: For pre-production validation
• Production: For live execution

Managing Scheduled Tasks

Once you've created a scheduled task, you can manage it from the web interface:

• View runs: See the history of task executions
• Interact with runs: Access logs and outputs
• Edit tasks: Modify prompts or frequencies
• Control tasks: Pause, resume, or delete tasks as needed

Related Resources

For more detailed information, check out the following resources:

• Getting Started Guide
• Build with Claude Code
• Deployment Guide
• Administration Guide
• [Configuration Guide](https://code.claude.com/docs/en/settings