Claude Code Routines: Schedule, API, and Webhook Automations on Anthropic's Cloud
Tools
TL;DR
- Claude Code launched Routines in research preview — configurable automations that pair a prompt, repo, and connectors.
- Routines run on Claude Code's web infrastructure, so no local laptop, cron job, or server is required.
- Three trigger types: Scheduled, API, and Webhook (starting with GitHub).
- Available now for Pro, Max, Team, and Enterprise plans with Claude Code on the web enabled — start at claude.ai/code or
/schedulein the CLI.
Anthropic has rolled out Routines in Claude Code, a new way to package recurring or event-driven development work as automations that run on Claude's own cloud. The unit is simple: a prompt, a repository, and the Claude Connectors you need. You set it up once, and Claude Code keeps running it according to whatever trigger you pick — without you having to babysit a long-lived process or maintain shared infrastructure for the team.
The first trigger type is Scheduled Routines, which run on a cadence you define — hourly, nightly, or weekly. A typical use case is pulling the highest-priority bug from Linear at 2am, attempting a fix, and opening a draft pull request before the team logs in. Another is scanning merged PRs every week, detecting where API changes drifted away from the documentation, and opening update PRs automatically. These extend the older /schedule CLI feature into a more reliable, cloud-hosted workflow (compare scheduling options).
API Routines give each automation its own endpoint and authentication token, which makes them easy to wire into existing systems. A CD pipeline can hit a Routine after each deploy to run smoke checks, scan error logs for regressions, and post the result to the right Slack channel. An alerting system like Datadog can stream alerts into a Routine that reads the payload, identifies the owning service, and drafts a triage summary so the on-call engineer sees a starting point rather than a raw alert.
Webhook Routines kick off in response to repository events, starting with GitHub. When a PR matches the filter you defined, Claude Code creates a session for it and keeps that session alive as new comments, CI failures, or follow-up commits arrive. This is well suited to focused review jobs — for example, watching changes to a sensitive module like /auth-provider and posting a structured summary to #auth-changes, or porting a merged PR from a Python SDK to its Go equivalent and opening the matching PR.
Routines are available today in research preview for Pro, Max, Team, and Enterprise plans with Claude Code on the web enabled. Usage counts against the same subscription budget as interactive sessions, with daily caps of 5 (Pro), 15 (Max), and 25 (Team and Enterprise) Routines per day. To create your first one, visit claude.ai/code or run /schedule in the CLI; the full setup details are in the Routines documentation.
Summary
- Claude Code Routines package a prompt, repo, and connectors as automations that run on Anthropic's cloud.
- Three triggers cover most automation needs: schedules, API calls, and GitHub webhooks.
- Common use cases: backlog triage, doc-drift detection, deploy verification, alert triage, and PR porting.
- Live for Pro, Max, Team, and Enterprise — start at claude.ai/code or check the Routines documentation.