claude-code - 💡(How to fix) Fix Local routines: support custom cron expressions in the UI [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52180Fetched 2026-04-23 07:34:29
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
1
Participants
Timeline (top)
labeled ×3

Local routines in the Claude desktop app currently only support preset schedule intervals (e.g. Daily, Weekly). There is no way to enter a custom cron expression through the UI, even though the remote routines API already supports arbitrary cron expressions via the cron_expression field.

Root Cause

  • Without custom cron support, one-time or non-standard schedules (e.g. "only on the 1st of each month", "once next Tuesday") are impossible via local routines.
  • As a workaround, users have to add a date guard inside the routine prompt itself (e.g. "check today's date and exit if it's not April 23") — which is a poor UX and wastes a session startup just to do nothing.
  • Remote routines already support this via cron_expression in the API, so the backend capability exists. The gap is purely in the local routine UI.

Fix Action

Fix / Workaround

  • Without custom cron support, one-time or non-standard schedules (e.g. "only on the 1st of each month", "once next Tuesday") are impossible via local routines.
  • As a workaround, users have to add a date guard inside the routine prompt itself (e.g. "check today's date and exit if it's not April 23") — which is a poor UX and wastes a session startup just to do nothing.
  • Remote routines already support this via cron_expression in the API, so the backend capability exists. The gap is purely in the local routine UI.
RAW_BUFFERClick to expand / collapse

Feature Request

Summary

Local routines in the Claude desktop app currently only support preset schedule intervals (e.g. Daily, Weekly). There is no way to enter a custom cron expression through the UI, even though the remote routines API already supports arbitrary cron expressions via the cron_expression field.

Current behavior

When creating a local routine, the schedule picker only offers fixed options (Daily, Weekly, etc.). There is no free-form cron input.

Desired behavior

Add a custom cron expression input option to the local routine schedule UI, equivalent to what the remote RemoteTrigger API already supports. For example, a user should be able to enter 0 10 23 4 * to fire once on April 23rd at 10 AM, or 0 9 * * 1-5 for weekdays only.

Why this matters

  • Without custom cron support, one-time or non-standard schedules (e.g. "only on the 1st of each month", "once next Tuesday") are impossible via local routines.
  • As a workaround, users have to add a date guard inside the routine prompt itself (e.g. "check today's date and exit if it's not April 23") — which is a poor UX and wastes a session startup just to do nothing.
  • Remote routines already support this via cron_expression in the API, so the backend capability exists. The gap is purely in the local routine UI.

Suggested UI

A "Custom" option in the schedule picker that reveals a cron expression text field, with a human-readable preview (e.g. 0 10 23 4 * → "At 10:00 AM, on day 23 of April").

Also consider a "Run once" option that auto-disables the routine after the first firing, which would cover the most common one-shot use case without requiring users to know cron syntax.

extent analysis

TL;DR

Add a custom cron expression input option to the local routine schedule UI to support arbitrary schedules.

Guidance

  • Introduce a "Custom" option in the schedule picker that reveals a cron expression text field, allowing users to enter custom schedules.
  • Implement a human-readable preview for the entered cron expression to improve user experience.
  • Consider adding a "Run once" option that auto-disables the routine after the first firing, covering common one-shot use cases without requiring cron syntax knowledge.
  • Ensure the custom cron expression input is validated and handled correctly by the existing remote routines API.

Example

No code snippet is provided as the issue focuses on the UI and feature request rather than specific implementation details.

Notes

The solution relies on the existing remote routines API supporting arbitrary cron expressions via the cron_expression field. The implementation should handle validation and error handling for custom cron expressions to prevent potential issues.

Recommendation

Apply workaround: Add a custom cron expression input option to the local routine schedule UI, as this directly addresses the feature request and provides the desired functionality.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Local routines: support custom cron expressions in the UI [1 participants]