claude-code - 💡(How to fix) Fix [FEATURE] Scheduled tasks should run reliably regardless of whether Claude Desktop is open [1 comments, 2 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#56194Fetched 2026-05-06 06:34:41
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
Timeline (top)
labeled ×2commented ×1unlabeled ×1

Root Cause

Example: Two weekly Monday tasks (SEO audit, site maintenance) both failed to run on their scheduled Monday because the app wasn't open at 8 AM. They were silently rescheduled to the following Monday with no indication anything was missed.

Fix Action

Fix / Workaround

The only known workaround is setting up macOS launchd plists to call the claude CLI on schedule — bypassing Claude Desktop's scheduler entirely. This is overly complex, undocumented, and defeats the purpose of having a built-in scheduler. There is no good in-product alternative.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

Problem Statement

Claude Desktop's scheduled tasks are client-side only — they fire only when the Claude Desktop app is open at the scheduled time. If the app is closed or the Mac is asleep, the task is silently skipped and rescheduled for the next occurrence (e.g., next week for weekly tasks).

This makes scheduled tasks unreliable for any user who doesn't keep Claude Desktop open 24/7. Weekly routines that miss their window are simply lost — there is no catch-up, no retry, no notification that a task was skipped.

Example: Two weekly Monday tasks (SEO audit, site maintenance) both failed to run on their scheduled Monday because the app wasn't open at 8 AM. They were silently rescheduled to the following Monday with no indication anything was missed.

Proposed Solution

Scheduled tasks should execute reliably regardless of whether Claude Desktop is open. The scheduler should either:

  1. Run as a background service / daemon that persists independently of the UI, so tasks fire at their scheduled time even when the app is closed, OR
    1. On next app launch after a missed window, detect the missed task(s) and offer to run them immediately, OR
    1. Integrate with the OS-level scheduler (macOS launchd / Windows Task Scheduler) at task creation time so the OS owns the trigger At minimum: notify the user when a task was skipped due to the app being closed, rather than silently rescheduling.

Alternative Solutions

The only known workaround is setting up macOS launchd plists to call the claude CLI on schedule — bypassing Claude Desktop's scheduler entirely. This is overly complex, undocumented, and defeats the purpose of having a built-in scheduler. There is no good in-product alternative.

Priority

Critical - Blocking my work

Feature Category

Configuration and settings

Use Case Example

I have weekly scheduled tasks (SEO audit, site maintenance) set to run every Monday at 8 AM and 9 AM. On Monday May 4, 2026, neither task ran because Claude Desktop was not open at those times. There was no notification. I only discovered the miss by checking task status manually. Both tasks were silently rescheduled to May 11 — an entire week of missed maintenance.

Additional Context

No response

extent analysis

TL;DR

Implement a background service or integrate with the OS-level scheduler to ensure scheduled tasks run reliably regardless of the app's state.

Guidance

  • Consider using a background service or daemon that can run independently of the UI to execute scheduled tasks.
  • Integrate with the OS-level scheduler (e.g., macOS launchd or Windows Task Scheduler) to leverage its reliability and persistence.
  • As a minimum, implement a notification system to inform users when a task is skipped due to the app being closed.
  • Explore using existing APIs or libraries that provide scheduling functionality to simplify the implementation.

Example

No code example is provided due to the lack of specific technical details in the issue.

Notes

The proposed solution requires significant changes to the existing architecture, and careful consideration should be given to the trade-offs between reliability, complexity, and user experience.

Recommendation

Apply workaround: Integrate with the OS-level scheduler to ensure reliable task execution, as it provides a robust and widely-supported solution.

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 [FEATURE] Scheduled tasks should run reliably regardless of whether Claude Desktop is open [1 comments, 2 participants]