Anthropic shipped a major feature this week: Routines. If you’re a team lead or decision-maker who pays for Claude, this one matters. If you’re the person fielding "should we use this?" questions from your team, this post is for you.
I’ll break down what Routines actually are, who they’re for, what to do with them right now, and what to ignore until it matures. This is what I do — I stay up to date with every Claude release so my clients don’t have to.
What are Routines?
A Routine is a saved Claude Code configuration: a prompt, one or more repositories, and a set of connectors — packaged once and run automatically. Think of it as a Claude task that runs on Anthropic’s infrastructure without your laptop being open.
That last part is the key shift. Until now, Claude Code automations required your machine to be running. Routines decouple the work from your hardware. A nightly bug triage, a weekly documentation check, a deploy verification — these can now run at 2 AM without anyone’s laptop lid being open.
Three ways to trigger a Routine
Routines come in three flavors, and each one serves a different purpose:
Scheduled Routines run on a recurring cadence — hourly, nightly, weekly. This is your classic cron job, but with Claude’s reasoning behind it. Example: every Monday morning, scan merged PRs from the past week and flag any documentation that references changed APIs.
API Routines give you a dedicated endpoint with an auth token. Your monitoring tools, CI/CD pipelines, or internal apps can call it on demand. Example: Datadog detects an error spike, hits the Routine’s endpoint, and Claude pulls the stack trace, correlates it with recent commits, and opens a draft PR with a proposed fix.
GitHub Routines listen for repository events — pull requests, releases, CI failures. Example: a PR is opened and the Routine automatically applies your team’s review checklist, leaving inline comments for security, performance, and style issues.
Who is this actually for?
Let me be direct: Routines are a developer-facing feature. If your team is primarily using Claude through the chat interface — Projects, Skills, and the conversational UI — Routines are not relevant to you yet.
Routines matter if:
- Your team has developers or technical ops people using Claude Code
- You have repetitive tasks that run on a schedule (triage, reporting, deploy checks)
- You’re integrating Claude into existing CI/CD or monitoring pipelines
- You’re on a Team or Enterprise plan and want to automate workflows across repos
If none of that describes your team, you can stop here. Bookmark this post and come back when your Claude usage matures.
What your team should actually do
If Routines are relevant to your team, here’s my recommended approach:
Start with one Scheduled Routine. Pick the most repetitive, low-stakes task your dev team does — something like "scan open issues and tag them by category" or "check if any documentation is out of date." Set it to run weekly. See how it performs before scaling up.
Don’t rush into API Routines. These are powerful but they require integration work. Don’t build a Datadog-to-Claude pipeline on day one. Wait until your team is comfortable with how Routines behave, what their failure modes look like, and how to debug them.
GitHub Routines are the highest-value starting point for dev teams. Automated PR review using your team’s actual standards is immediately useful. The ROI is obvious: every PR gets a consistent first pass before a human reviewer touches it.
What to ignore (for now)
Every time Claude ships a feature, there’s a wave of "this changes everything" posts. Let me tell you what to filter out:
- Don’t try to automate complex decision-making. Routines are great for triage, checks, and drafts. They’re not ready to make judgment calls about your architecture or your product roadmap.
- Don’t burn your daily limits experimenting. Pro gets 5 routines/day, Max gets 15, Team and Enterprise get 25. Budget them like you would any constrained resource.
- Don’t confuse Routines with a no-code automation platform. This is Claude Code. It requires technical comfort. If your team isn’t already using Claude Code, adding Routines won’t change that.
The bigger picture
Here’s what I tell my clients: every Claude release makes the gap wider between teams that have a strategy and teams that are winging it.
Routines are a perfect example. A team with a clear Claude blueprint knows exactly where this fits: "We’re already using Claude Code for X. Routines let us automate the repetitive parts of X. Here’s which ones we’ll set up and who owns them." That conversation takes 15 minutes.
A team without a strategy hears "Routines" and adds it to the pile of Claude features they’ve heard about but haven’t evaluated. Skills, Projects, MCP connectors, Claude Code, Cowork, and now Routines — it’s overwhelming when you don’t have a framework for deciding what matters.
That’s the real cost of not having a Claude strategy. It’s not that you’re missing one feature. It’s that every new feature makes the decision space larger and the catch-up more expensive.
What this means for non-technical teams
If your team doesn’t touch code, Routines aren’t your priority. But here’s what you should pay attention to: the pattern. Anthropic is steadily moving Claude from "chat assistant" to "autonomous worker." Routines today, more agentic features tomorrow.
The teams that are set up with Projects, Skills, and connected tools right now will be best positioned when the next wave of automation features arrives. The foundation matters more than any single feature.
Need help figuring out where Routines (or any Claude feature) fits into your team’s workflow? That’s exactly what the Clarity Session is for. Nicole maps your tools, your workflows, and your team — then tells you what to use, what to skip, and in what order. Book a free 15-minute call to see if it’s the right fit.
Nicole Patten is the founder of Elevate Online and one of fewer than 10 Claude-specific training providers globally. She spent 7 years at Google as a Senior UX Engineer before dedicating her career to helping teams use AI responsibly and effectively. 100% of her business runs on Claude.