Claude Routines for Engineering Teams: What to Automate

TL;DR: A practical guide to Claude Routines, what to automate, what to avoid, how triggers work, usage limits, and how they compare to GitHub Actions.

Claude Routines are saved cloud agent configurations that run on Anthropic's infrastructure, triggered by schedules, API calls, or GitHub events. They launched on April 14, 2026, in research preview. For engineering teams already using Claude Code, Routines are the natural next step, but what you automate first matters more than the fact that you can automate at all.

A Routine is not a CI pipeline step. It is an AI agent with full Claude Code capabilities, reading code, making judgment calls, writing changes, and creating pull requests. That distinction changes what is worth automating and what is too risky to hand over.

How Routines Work

A Routine bundles four elements into a reusable, triggerable unit:

Prompt, the instruction for the agent (what to do, how to report, what to skip)
Repositories, which codebases the agent can access
Environment, settings, MCP servers, and connectors
Triggers, when and how the Routine starts

Trigger Types

Trigger	How it fires	Best for
Scheduled	Hourly, daily, nightly, weekdays, or weekly	Recurring audits, reports, dependency checks
API	HTTP POST to a per-routine endpoint with bearer token	Integration with CI/CD, Slack bots, internal tools
GitHub	pull_request.opened, push, issues.opened, releases, check_run	PR review, issue triage, release note generation

A single Routine can combine all three triggers. A nightly dependency audit could also fire on every push to a specific branch.

Execution Model

Routines run on Anthropic's cloud infrastructure. They do not require your laptop to be open. A Routine triggered at 2:00 AM executes on Anthropic's servers, completes its work, and the results are waiting when you open the app in the morning.

Daily Limits

Routines are in research preview and Anthropic does not publish fixed per-plan run counts; limits change as the feature matures. Each account has a daily cap on how many Routine runs can start. Check your current remaining allowance at claude.ai/code/routines or claude.ai/settings/usage.

When a Routine hits the daily cap or your subscription usage limit, accounts with extra usage enabled can continue on metered overage. Enable extra usage from Settings > Billing on claude.ai.

Runs draw from the same usage pool as interactive sessions. A Routine that burns through tokens at 3:00 AM leaves fewer tokens for your 9:00 AM coding session.

What to Automate First

Start with tasks that have three properties: low blast radius (if the agent gets it wrong, the cost is low), high frequency (runs often enough to justify setup), and clear success criteria (the agent can verify its own output).

Tier 1: Start Here

Nightly issue triage. The agent reads open issues, labels them by priority and component, and posts a summary to a Slack channel or a Markdown file. If it mislabels an issue, a human corrects it in the morning: low cost, high learning.

Weekly dependency audit. The agent checks for outdated dependencies, known vulnerabilities, and licence compliance. It writes a report; it does not update anything. Read-only Routines are the safest starting point.

PR description enrichment. On pull_request.opened, the agent reads the diff and adds a structured summary, test coverage assessment, and reviewer suggestions to the PR description. It adds context; it does not approve or merge.

Tier 2: After Confidence Builds

Automated PR review comments. The agent reviews code changes and leaves inline comments on potential issues. This requires more trust: a bad review comment wastes reviewer time. Start with a narrow scope (one repository, one language).

Release note generation. On releases.published, the agent reads the commits since the last release and generates categorised release notes. Useful, but the output should be reviewed before distribution.

Test gap analysis. Nightly scan of changed files versus test coverage. The agent identifies functions that changed but have no corresponding test changes. Reports only, does not write tests.

What NOT to Automate (Yet)

Production deployments. Routines should never trigger a production deploy. The blast radius is too high and the rollback path through a Routine is not established.

Customer-facing content changes. Any Routine that modifies content visible to end users (documentation sites, support articles, marketing pages) needs human review before publish.

Security-sensitive operations. Routines that touch authentication, authorisation, encryption, or infrastructure configuration should remain manual until the Routines permission model matures beyond research preview.

Cross-repository changes. A Routine that modifies multiple repositories in one run creates a coordination problem. If it fails halfway, partial changes across repos are harder to unwind than a single-repo revert.

Routines vs GitHub Actions

The comparison is natural but misleading. They solve different problems.

Dimension	GitHub Actions	Claude Routines
What runs	Shell scripts, containers, predefined actions	An AI agent with reasoning, code comprehension, and judgment
Trigger types	Push, PR, schedule, workflow_dispatch	Schedule, API, GitHub events (same set, different execution)
Output	Pass/fail, logs, artefacts	Code changes, PR comments, reports, new issues
Determinism	Deterministic (same input = same output)	Non-deterministic (model output varies)
Cost model	Minutes-based, free tier available	Token-based, draws from subscription
Best for	Build, test, deploy, lint	Triage, review, analysis, report generation

They complement each other. Use GitHub Actions for deterministic operations (build, test, deploy). Use Routines for tasks that require judgment (triage, review, gap analysis).

Governance Considerations

Routines execute on Anthropic's infrastructure with access to your repositories. This creates governance questions that your AI security posture should address:

Repository access scope. Which repositories should Routines be able to read? Which should they be able to write to?
Secret exposure. If a Routine has access to a repository, does it also have access to that repository's secrets? Verify before enabling.
Audit trail. Routine runs produce logs, but are those logs accessible to your security team? Where are they stored?
Approval for new Routines. Who can create a Routine? If any developer on the team can create a Routine that reads any repository on a schedule, you have a governance gap.

Teams that have already built their AI acceptable use policy should update it to cover Routines explicitly.

Frequently Asked Questions

Can Routines create and merge pull requests?

Yes. A Routine has full Claude Code capabilities, which includes creating branches, committing changes, opening PRs, and, if configured, merging them. Whether it should merge is a governance decision, not a technical one. Most teams start with Routines that create PRs for human review.

Do Routines work with private repositories?

Yes. Routines connect to repositories through your Claude Code configuration. Private repositories are accessible if your authentication is configured correctly.

What happens if a Routine fails?

The run stops and the failure is logged. Partial work (uncommitted changes, draft PRs) depends on where the failure occurred. Routines do not have built-in rollback, if a Routine pushes a bad commit, you revert it the same way you would revert any other commit.

Are Routines available on the Claude API (not just the app)?

Routines are currently available through Claude Code on the web. API-triggered Routines use HTTP POST to a per-routine endpoint. Direct SDK integration for Routines is not yet available.

Get Your Routines Strategy Right

If your team is evaluating Claude Routines but you are not sure what to automate, what to protect, or how to update your governance for scheduled agents, start with a structured assessment.

Our AI Readiness Assessment evaluates your current AI tool posture and identifies the specific governance updates needed for autonomous agent capabilities like Routines.

If you are ready to design the operating model for scheduled agents across your engineering organisation, our AI Consulting services can help.

Claude Routines for Engineering Teams: Scheduled Agents, GitHub Triggers, and What to Automate First