2026-05-07

Claude Code Routines in research preview: schedule agents like cron jobs, no laptop required

Anthropic ships Claude Code Routines — a (prompt, repo, connectors) config that runs on Anthropic infra, triggered by schedule, HTTP POST, or GitHub event.

Announced at the Code with Claude SF conference on May 6, Anthropic shipped Claude Code Routines in research preview. A Routine is a (prompt, repo, connectors) configuration that runs on Anthropic’s infrastructure — not your machine — triggered by a schedule, an HTTP POST to a per-routine endpoint, or a GitHub event such as a pull request or release.

How it works

You define three things:

Prompt — the task description, written the same way you’d prompt Claude Code interactively.
Repo — a GitHub repository the agent can read from and write to.
Connectors — optional integrations (Slack, Linear, Datadog, etc.) the routine can post to.

Anthropic provisions the execution environment. The agent runs, does the work, and reports back. No local runner, no GitHub Actions YAML, no persistent server.

Trigger types and rate limits

Trigger	Notes
Schedule (cron)	Standard cron syntax
HTTP POST	Per-routine webhook endpoint
GitHub event	PR opened, release created, commit pushed, etc.

Run quotas: Pro = 5/day, Max = 15/day, Team/Enterprise = 25/day.

Documented use cases from the launch

Nightly issue triage with Slack summaries
Weekly docs-drift PR generation (checks if docs match current code)
Post-deploy smoke test pipelines
Datadog alert triage → opens GitHub issues with root cause candidates

How this compares to alternatives

Before Routines, building this required: a self-hosted runner (EC2, Fly.io, GH Actions runner), a GitHub Actions workflow to handle triggers, and a custom harness around the Claude API. Routines collapses all three into a single configured object.

For GitHub-triggered workflows, Routines is a direct competitor to GitHub Copilot Workspace for automated PR review and documentation maintenance. The key advantage is that Routines uses the full Claude Code agent (with file reads, edits, web search, MCP tool access) rather than a purpose-built code-review model.

Practitioner note

For teams on Max or Enterprise (15–25 runs/day), the practical test is to migrate one existing cron-based agent task to a Routine and measure the operational overhead reduction. The GitHub trigger integration is the most valuable feature: setting up a Routine to open a PR whenever a GitHub issue is labeled needs-docs is a task that previously required a custom GitHub App. Start with a low-stakes, high-frequency task to calibrate the run quota before moving critical workflows.