Anthropic debuts ‘routines’ in Claude Code to automate recurring dev workflows

Anthropic has introduced Routines in Claude Code in research preview, aiming to automate recurring engineering tasks without the need for custom schedulers or infrastructure.

Built on Claude Code’s web platform, routines run in the cloud, which means nothing depends on a developer’s laptop being switched on. It is a quiet shift, but a meaningful one.

From manual repetition to automated workflows

Engineering teams often repeat the same set of tasks. Reviewing pull requests, triaging bugs, updating documentation, or responding to alerts. Until now, automating these required stitching together cron jobs, scripts and third-party tools.

Routines changes that. It packages these recurring activities into reusable automations that can run independently. Once configured, they can execute on a schedule, respond to events or be triggered via API.

In simple terms, it turns tasks into systems.

Why routines solve a real problem

Most teams already use AI tools to speed up coding or reviews. But these interactions are still manual.

Routines aim to standardise this process. They automate tasks, keep workflows consistent, and reduce reliance on custom infrastructure.

This also improves handoffs between humans and AI. Instead of ad hoc usage, workflows become predictable and reliable.

3 ways to trigger a routine

Anthropic has introduced three trigger modes, each designed for different use cases.

Scheduled routines

These run at fixed intervals such as hourly, nightly or weekly. For example, a routine could pick the top bug from a tracker at 2 am, attempt a fix, and open a draft pull request.

API routines

Each routine gets its own endpoint and token. Internal systems can send data and receive a session link in return. This is useful for deploy checks, alert systems or dashboards.

Webhook routines

Starting with GitHub, routines can respond to repository events. For instance, every pull request can trigger a review session that continues tracking updates like comments or CI results. Together, these modes cover most real-world automation needs.

No infrastructure, no maintenance

One of the biggest advantages is simplicity. Routines run entirely on Claude Code’s infrastructure. Teams don’t need to maintain servers, set up schedulers, or monitor uptime. This reduces operational overhead, especially for smaller teams. It also makes scaling easier. Workflows that once required engineering effort can now be configured in minutes.

Routines are available on Pro, Max, Team and Enterprise plans, can be created via web, CLI or API, and come with daily run limits based on the subscription, with the option to scale further.

Why this matters for developers?

For teams in India and globally, this could reduce the reliance on custom scripts tied to individual machines.

It also introduces a more structured way to use AI in production environments. According to Dario Amodei, the focus is on building reliable, safety-aligned systems. Routines fits that vision by offering controlled, auditable automation rather than one-off experiments.