Claude Code Routines automates scheduled developer admin

For development teams at UK SMEs, this closes a gap that has existed since AI coding tools became mainstream. Repetitive admin tasks like nightly bug triage, weekly documentation checks, and post-deploy verification have always required a developer's time or a separate automation stack. Routines fold that into the tool developers are already using.

What Routines are and how they work

Until now, Claude Code worked session by session. A developer opened a session, issued a prompt, and received a result. Repeating a task meant repeating the session. Automation required cron jobs, MCP servers, and additional infrastructure to manage alongside the codebase.

Routines remove that overhead. You write a prompt, point it at a repo and any relevant connectors, set a trigger, and Claude Code handles execution on its own cloud infrastructure. Three trigger types are available at launch.

Scheduled routines

Set a task to run hourly, nightly, or weekly. A nightly prompt like "pull the top bug from Linear, attempt a fix, and open a draft PR" runs automatically at 2am without anyone present. If you have been using the /schedule command in the Claude Code CLI, those tasks have now become scheduled routines.

API routines

Every routine gets its own endpoint and authentication token. POST a message to the endpoint and receive back a session URL. This lets you wire Claude Code into alerting systems, deployment hooks, or internal dashboards. An on-call team can point a monitoring tool at the endpoint and Claude Code will correlate the alert with recent deployments before the engineer opens the page.

Webhook routines

Subscribe a routine to fire in response to GitHub events. Open a PR touching a sensitive module and Claude Code opens a session, runs your defined checklist, and posts inline comments before a human reviewer arrives. Anthropic plans to expand webhook sources beyond GitHub in the coming months.

The pattern gecco clients will recognise

If your team uses Cowork's Schedules feature, Claude Code Routines follows the same logic, applied to codebases rather than documents and workflows. Configure once, trigger automatically, receive an output. The underlying principle is identical: remove the human from tasks that do not need a human present.

At gecco, we see this as consistent with the direction AI tooling has been heading for two years. The tools that save the most time are the ones that run without prompting. Our Automations service does this for business processes across 7,000+ platforms. Routines extend that principle into the development environment itself.

Practical applications for UK SME development teams

The use cases Anthropic highlights at launch map well to tasks that cost development teams real time each week.

Nightly bug triage: pull new issues from your tracker, label and assign them, and post a summary to a Slack channel. No one starts their morning with an unreviewed backlog.

Documentation drift detection: scan merged PRs weekly, flag documentation referencing changed APIs, and open update PRs automatically before the gap becomes a support problem.

Deploy verification: have Claude Code run smoke checks and scan error logs after each deployment, posting a go/no-go to the release channel before on-call picks it up.

Bespoke PR review: set a routine to run your team's security and performance checklist on every opened PR, leaving inline comments before a human reviewer reaches it.

SDK porting: merge a change to one language SDK and a routine opens a matching PR in the parallel SDK automatically.

Each of these tasks exists in most development teams. Most are handled manually, inconsistently, or deferred until they become a problem. Routines make the consistent version the default.

Availability and limits

Routines are available in research preview for Claude Code users on Pro, Max, Team, and Enterprise plans with Claude Code on the web enabled. Daily limits apply: Pro users can run five routines per day, Max users 15, and Team and Enterprise users 25. Additional runs beyond those limits are available with extra usage. Routines draw from the same subscription usage as interactive sessions.

The research preview status matters. Features in research preview can change. Early adopters should build routines into workflows they can monitor closely, not processes they cannot afford to watch.

A note on scope

Routines are a developer tool. They require access to a codebase, a Claude Code subscription, and technical confidence to configure well. They are not a general-purpose automation feature for non-technical teams.

That distinction matters for SMEs with mixed workforces. If your business needs scheduled AI-driven tasks outside the codebase, such as CRM updates, document generation, or data flows between platforms, gecco's Automations service covers that ground using n8n and Zapier. Routines and Automations are complementary, not interchangeable.

Next step

If your development team has recurring manual tasks sitting in a backlog or a morning rota, Routines is worth testing this week. Start with a single nightly task, review the output for a few days, then expand. If you want a clearer read on where AI fits across your business, take the AI readiness assessment: https://forms.geccohq.com/r/kdYrVd