Closing the automation gap in Claude Code

Claude Code Desktop introduced scheduled tasks last year, and I immediately started using them. Morning standup prep that summarized yesterday's commits, end-of-day PR digests, a weekly dependency audit — all running on a timer without me touching anything. For simple recurring prompts, it worked. Then I tried to build something more involved. I wanted a task that ran every morning before I started work — reviewing open PRs, summarizing what changed overnight, and flagging anything that needed my attention. A straightforward cron job, except the worker is Claude instead of a bash script. Two problems surfaced quickly. First, the built-in scheduler requires the Desktop app to be running. The app is resource-heavy, and keeping it open around the clock just to service a few scheduled tasks felt wrong — I didn't want to dedicate those resources to a process I wasn't actively using. Second, the scheduled execution environment is sandboxed differently from an interactive session. Prompts and