Claude Code Launches Cloud-Based Task Scheduling for Automated Development Workflows
#DevOps

Claude Code Launches Cloud-Based Task Scheduling for Automated Development Workflows

Startups Reporter
3 min read

Anthropic's Claude Code introduces scheduled tasks that run autonomously in the cloud, enabling developers to automate recurring workflows like PR reviews and CI failure analysis without keeping machines on.

Anthropic has expanded its Claude Code offering with cloud-based task scheduling, allowing developers to automate recurring workflows that run independently of their local machines. The new feature, available to all Claude Code on the web users including Pro, Max, Team, and Enterprise tiers, enables autonomous execution of prompts on a recurring cadence using Anthropic-managed infrastructure.

Three Scheduling Options Compared

Claude Code now provides three distinct approaches to scheduling recurring work, each suited to different use cases:

Cloud Tasks run on Anthropic's infrastructure, requiring no local machine to be on and no active session. These tasks can execute every hour minimum and maintain persistent state across restarts. However, they cannot access local files directly.

Desktop Tasks execute on the user's machine using the /loop command. These require the machine to be powered on and a session to be open, but provide full access to local files and tools. They're ideal for quick polling during active development sessions.

CLI Scheduled Tasks offer a middle ground, allowing users to set up recurring prompts through the command line interface that run in cloud environments.

Creating Cloud Tasks Through Multiple Entry Points

Users can create scheduled tasks through three interfaces: the web portal at claude.ai/code/scheduled, the Desktop app's Schedule page, or directly from the CLI using /schedule. The web and Desktop interfaces present a form-based workflow, while the CLI guides users through setup conversationally.

Task Configuration Deep Dive

The task creation process involves several key configuration steps:

Naming and Prompt Writing - Users provide a descriptive name and write a self-contained prompt that explicitly defines success criteria. The prompt includes a model selector, determining which Claude model executes each run.

Repository Selection - Tasks can work across multiple GitHub repositories, each cloned from the default branch at runtime. Claude creates claude/-prefixed branches for changes by default, with an option to allow unrestricted branch pushes when needed.

Environment Setup - Users select from cloud environments controlling network access, environment variables for API keys and secrets, and setup scripts for installing dependencies before each run.

Scheduling - The interface offers preset frequencies including hourly, daily (defaulting to 9:00 AM local time), weekdays, and weekly options. Tasks may run a few minutes after scheduled times due to staggering.

Connector Management - All connected MCP (Model Context Protocol) connectors are included by default, enabling tasks to interact with external services like Slack, Linear, or Google Drive. Users can remove unnecessary connectors to limit tool access.

Managing and Monitoring Tasks

Once created, tasks appear in the scheduled tasks list and run automatically. Each execution creates a new session where users can review Claude's work, examine changes, and create pull requests. The detail page for each task shows repositories, connectors, prompt, schedule, and past runs.

Users can trigger immediate runs with "Run now," pause schedules with a toggle, edit configurations, or delete tasks entirely. Past sessions remain accessible in the session list even after task deletion.

Practical Use Cases

The feature enables several common development workflows to run autonomously:

  • Daily PR Reviews - Automated analysis of open pull requests each morning
  • CI Failure Monitoring - Overnight analysis of continuous integration failures with summarized findings
  • Documentation Synchronization - Post-merge documentation updates
  • Dependency Audits - Weekly security and version checks

Technical Architecture

Cloud tasks execute in isolated sessions with fresh repository clones for each run. The infrastructure handles authentication, environment setup, and connector initialization automatically. Tasks can run autonomously without permission prompts, making them suitable for unattended operations.

For developers needing local file access or real-time interaction, Desktop tasks remain available through the /loop command. The CLI also supports lightweight scheduling within active sessions for quick polling needs.

Getting Started

New users can access the feature by visiting claude.ai/code/scheduled and clicking "New scheduled task." The guided setup walks through each configuration step, with the CLI offering an alternative conversational approach using /schedule.

The addition of cloud-based task scheduling represents Anthropic's continued expansion of Claude Code beyond simple code assistance toward comprehensive development workflow automation.

Comments

Loading comments...