### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet - [x] This is a single feature request (not multiple features) ### Problem Statement Today, local routines can only run at most once per hour. I'm not sure why this restriction exists since you can work around it with `/loop Xm xyz` or with duplicate hourly routines. I expect this is for cloud routines

[FEATURE] Allow more frequent local routines

Status Fixed / completed

Maintainer reply ✓ Yes — bcherny

Workaround ✓ Mentioned in thread ↓

Activity 4 comments · opened Jun 28, 2026 · closed Aug 17, 2026

💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

Preflight Checklist

[x] I have searched existing requests and this feature hasn't been requested yet
[x] This is a single feature request (not multiple features)

Problem Statement

Today, local routines can only run at most once per hour. I'm not sure why this restriction exists since you can work around it with /loop Xm xyz or with duplicate hourly routines. I expect this is for cloud routines but it's extended to local.

Proposed Solution

Allow any valid cron expression for local routines. Or at minimum allow sub-hourly cron expressions.

Alternative Solutions

I am working around it by making duplicate hourly routines that run on different points in the hour 🙃 .

A more user-friendly solution would be a better "custom" scheduler, but that would be gravy.

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

3 Comments

PigLardLord · 2 months ago

Related: #79831 — [FEATURE] Trigger a local routine on demand via a local command / IPC (not only cron). Complementary angle: this issue tightens the schedule (sub-hourly cron), while #79831 adds an on-demand / event-driven entry point so local automation doesn't depend on cron granularity at all.

bcherny collaborator · 1 month ago

Local scheduled tasks (Desktop) can run more often than hourly today — the schedule picker only offers presets, but you can ask Claude in any Desktop session to set a custom interval, e.g. "schedule a task to run all the tests every 15 minutes." Details: https://code.claude.com/docs/en/desktop-scheduled-tasks

The one-hour minimum applies to cloud routines (https://code.claude.com/docs/en/routines). In the CLI, /loop 5m <prompt> accepts any cron interval within a session (https://code.claude.com/docs/en/scheduled-tasks).

🤖 Generated with Claude Code

andrewneilson · 1 month ago

Local scheduled tasks (Desktop) can run more often than hourly today — the schedule picker only offers presets, but you can ask Claude in any Desktop session to set a custom interval, e.g. "schedule a task to run all the tests every 15 minutes." Details: https://code.claude.com/docs/en/desktop-scheduled-tasks

Hi @bcherny , yes I know you can work around it. My request was simply to remove the unnecessary restriction from the cron expression option in the UI for local routines. My screenshot is for a local routine in claude desktop. Not for a cloud routine.

This is still true in Claude 1.32885.1 (a757f5) 2026-08-18T19:00:11.000Z

Showing cached comments. Read the full discussion on GitHub ↗