Claude Code Routines are here! In addition to a schedule, you can now trigger templated agents via GitHub event or API – with our infra & your MCP+repos They've changed how we do docs, backlog maintenance and more internally at Anthropic Get started at

A personal favorite: 1-click Github Events to trigger templated Routines. We use these internally to synthesize docs whenever a PR is merged into our release branch.

Wildcard Functionality: Every Routine now comes with an API endpoint (that also takes a message parameter) so you can fire off agents from your alerting stack, Zapier, or wherever else!

Good ol’ cron: and of course, we still support scheduling since it’s an oldie and a goodie and powers all sorts of useful backlog maintenance and triage workflows.

You can now create unlimited routines. Every plan comes with a number of included daily runs which use your subscription and after that let you know when it’s time to switch on Extra Usage

Get started today at

fix your infra

sick - this works without having to have your computer be on all the time?

👀

:)

Please stabilise your product before shipping new features, the feeling is off recently and customers are looking for alternatives, you're just one model away from losing all good customers who have faith in your company.

The folks at @AnthropicAI are working hard, shipping tons of features every day, but in the end, users will only use about 5% of them 🙃

Wow ya'll will do anything accept build a normal basic API for Claude Code Web Runs. The Remote Agents SDK is an over complicated primitive for non-coding agents. Routines is over specialised. Just let us have the same basic API that Claude Code CLI & Desktop uses to delegate to Web Runs?!

What is the difference between the /schedule and the routine triggered by a cron ? For the rest I agree this very cool

/schedule directly creates a Routine (scheduled cloud sessions just nested under routines)

@Marc87240 I thought /schedule needs your laptop to be running?

@noahzweben Nope you can use /schedule to set up tasks with cloud env

@noahzweben Then the naming is confusing 😅 Both features with similar names have overlaps.

@noahzweben Yeah true loop schedule and now routine but anyway the routine feature is very excellent and the limit is way higher. Game changer imo

Great ship! We've been using scheduled Routines for a while now to update so there's no drift between feature ship and help docs. Which has been lkey amazing. But to do it via API in CI/CD vs on a periodic schedule = 🔥

Was just browsing the usage section on the desktop app and saw that it includes a new section. 5 routines a day included with my Max 5x plan

Oops - meant to be 15 for Max. Check again :)))

@abhi2601k Is it 15 for x5 max and 20x max? Seems like many users could downgrade if so?

@noahzweben Surely you’re not paying for included Routines when you pay $200. Would a user who uses as much as the 20x limits be okay with 4 times less limits at 2x less the price?

github event triggers are the quiet part of this launch. schedule-based agents are useful. event-driven agents are a different category. "run this agent every time a pr lands" turns claude code from a coding assistant into a ci primitive. that's a much bigger surface area than the docs demo suggests.

Okay fine, can I work at @anthropic? This is getting silly, you're literally building all of my ideas.

Please just stop for a bit the updates and focus on fix the viral problems

Love Routines but what I actually need: one Claude orchestrator I talk to from any device that dispatches work to my always-on Mac Studio running Claude Code. Ephemeral cloud containers can't run Roblox/Chrome/Blender. I don't need more cron jobs. I need an agent coordinator layer.

This is what we have been duct-taping with scheduled tasks. 26 agents on heartbeats, each with its own spec and output path. Native routine support with GitHub triggers means half the orchestration layer gets replaced by infra. Watching this closely.

Already found a perfect use case:

this is a game changer for dev workflows, ngl the integration with GitHub events will streamline a lot of processes fr

Is this schedules but for Claude Code? gaddamn so many things to keep track of

congrats

this is sick

Thank you!

Thank you for your project, it will make many people unemployed and increase the number of suicides

the github event trigger is the one that really changes things, been waiting for something like this to wire agents into actual dev workflows

how is this different from a cron

Do we need to be on a team plan so other team members can collaborate on my routines?

the "changed how we do docs and backlog maintenance internally at Anthropic" part is the most interesting line. dog-fooding agentic routines for actual PM work is a very different signal than a demo.

try - like "Claude Managed Agents" but without the vendor lock, built for enterprise SDLC. runs on your own infrastructure, full governance & monitoring, bring your own model from any provider. automates your dev workflows and continuously self-improves. your stack, your rules.

anthropic finally admitting that their internal docs were a mess and they needed an api to fix it? cool story, now show me the revenue model since i doubt these routines are generating more than maintenance costs

@trq212 So Claude started automating my daily routine.

Solid insight. What's your debugging workflow when you're really stuck?

whoa this is a game changer ngl can't wait to see how it all works

Am I the ONLY one who thought the background music was Fantasy by Ludacris? 😭

When will gitlab support comes out