Claude Code Routines vs OpenHelm: Why Local Wins at the 5-Run Limit

On 14 April 2026, Anthropic launched Claude Code Routines — a built-in scheduler that lets you run Claude Code tasks automatically on a timed basis. No third-party tools, no cron, no wrangling with shell scripts. It's a genuinely useful addition for developers who want a starting point.

But there's a limit buried in the pricing page that's worth knowing about before you build workflows around it.

The Cap That Changes Things

Claude Code Routines runs your jobs in Anthropic's cloud. That comes with daily run limits tied to your subscription plan:

• Pro plan: 5 routine runs per day
• Max plan: 15 routine runs per day

For occasional use — running a morning standup summary or a weekly dependency audit — 5 a day is probably fine. But if you're trying to automate a meaningful chunk of your development workflow, 5 runs isn't much. Five jobs across a 24-hour period means you need to choose carefully which tasks get automated and which don't.

Power users on the Max plan get 15. Still, if you've got code review bots, test runners, documentation generators, and deployment scripts, 15 slots can disappear quickly.

"I hit the Routines limit on day three. I was running four jobs per project and I'm actively developing two projects. It's not a criticism — I understand why it's capped — but I had to rethink my setup." — Developer in the OpenHelm community Discord, April 2026

What Routines Actually Does Well

Before getting into the limits, it's worth being fair. Claude Code Routines is a clean solution for what it targets. Setup is fast — you define a schedule directly in Claude.ai, no external tooling required. Jobs run in Anthropic's infrastructure, so you don't need your Mac switched on. There's no config file to maintain and no shell wrapper to debug.

For teams or individuals who want a lightweight way to run a handful of recurring tasks, Routines is a solid choice. If you're running, say, a weekly codebase health report and a daily changelog summary, you'll never touch the limit.

The problem arises when you scale past that use case.

Three Constraints That Matter

1. Run limits

As above — 5/day on Pro, 15/day on Max. These are hard limits. Once you've used your allocation, jobs queue for the next day.

2. No local file access

Claude Code Routines clones your git repository to run jobs. That's a deliberate design choice for security and reproducibility, but it means your routine can't access environment variables set on your local machine, files that aren't committed to git, or any tooling installed in your local environment. If your workflow depends on local context — .env files, custom toolchain setup, uncommitted work-in-progress — Routines can't see it.

3. Cloud-only execution

You can't run Routines on your own machine. If you need local-first execution for compliance reasons, data sensitivity, or simply to avoid the latency of cloud scheduling, Routines isn't the right fit.

How OpenHelm Approaches the Same Problem

OpenHelm is a macOS desktop app that runs Claude Code jobs locally — on your machine, against your local filesystem, with access to your full environment. No run limits; you can schedule as many jobs as you need.

Here's how the two compare directly:

The trade-off is clear: Routines wins on "works without your Mac". OpenHelm wins on everything that requires your local environment.

When You'd Choose Routines

You want zero maintenance. No app to update, no daemon to manage. Routines just runs.

Your workflows are git-centric. If everything you're automating lives in committed code with no local dependencies, Routines fits naturally.

You don't need more than 15 jobs per day. Power users on Max will find 15 slots generous for focused automation.

You travel and want jobs to run when your laptop is closed. Routines is cloud-hosted, so your Mac being off is fine.

When You'd Choose a Local Alternative

You need local file and environment access. Any job that reads .env, uses local credentials, or depends on locally installed tooling won't work in Routines.

You're running more than 5–15 jobs per day. CI/CD automation, multi-project scheduling, frequent check-in jobs — these exhaust the Routines allocation quickly.

You want control over your execution environment. Local execution means you know exactly where Claude Code runs, which dependencies it has access to, and what it can and can't touch.

You want structured failure handling. OpenHelm's silence detection, self-correction loop, and crash recovery are designed for jobs that run unsupervised — features that matter when you're not watching.

The Practical Middle Ground

Some developers are running both. Routines for jobs that are genuinely git-centric and don't need local context — cloud-friendly automation like repo health checks or PR summaries. OpenHelm for everything that touches local files, needs more than 15 runs a day, or requires the full silence detection and recovery stack.

That's a reasonable setup. The tools aren't mutually exclusive.

What to Do If You've Hit the Limit

If you're reading this because you've hit the Routines cap and you need more runs, the quickest path is:

1. Install OpenHelm from openhelm.ai — the free tier covers common single-developer use cases.
2. Migrate your jobs — OpenHelm uses the same Claude Code prompts, so there's nothing to rewrite. Just define the schedule and the task.
3. Run both in parallel if you want — keep Routines for cloud-native jobs, use OpenHelm for local-first work.

The two tools were built with different constraints. Knowing which constraints apply to your workflow makes the choice obvious.

---

TL;DR: Claude Code Routines is a capable cloud scheduler with a 5-run/day cap on Pro and 15/day on Max. It doesn't access local files or environment variables. If you need unlimited runs, local file access, or advanced failure handling, a local scheduler like OpenHelm is the better fit — and the two can run alongside each other.

FAQs

Can I increase my Claude Code Routines limit?

Only by upgrading to a higher plan. Max gives you 15/day versus Pro's 5. There's no way to purchase additional routine slots separately.

Does OpenHelm replace Claude Code Routines entirely?

Not necessarily — it depends on your workflow. If you need cloud-based execution (your Mac off, jobs still run), Routines covers that. OpenHelm is the right choice when local file access, unlimited runs, or advanced failure handling matter more.

Will Claude Code Routines ever increase the daily limits?

Anthropic hasn't announced changes, but the feature launched in April 2026, so limits could shift as it matures. Check the Claude pricing page for current limits.

Is OpenHelm open source?

No. OpenHelm is Fair Source (BSL 1.1). The open source Claude Code schedulers guide covers fully open source options if that's a requirement.

What happens to queued Routines jobs when I hit the daily limit?

They queue for the next day's allocation. You can't prioritise or reorder the queue.