Work & OperationsDone with Claude Code Apr 11, 2026
Run nightly briefing pipelines with scheduled tasks
The author uses Claude Code cloud scheduled tasks for nightly pipelines that scan work, generate retrospectives, and assemble morning briefings.
- What They Did
- The author had a self-hosted Claude automation stack with three environments, 11 cron jobs, and a Slack daemon, then mapped which jobs could move to Claude Code Cloud scheduled tasks. In Cloud, nightly retrospectives and the morning orchestrator run sequentially, using git as the handoff between fresh task runs; hourly tasks read from git or call APIs directly for tweet scheduling, email processing, and news monitoring, while each task commits its own output.
- How It Went
- The migration would remove 7 of 11 cron jobs because they only existed to keep the system alive, and the author says the sequential Cloud runs can improve quality by keeping one session’s context. It still falls short for the always-on Slack workflow, because Cloud tasks start in a fresh VM and cannot listen continuously for messages.
- Worth Knowing
- The main catch is architectural: every Cloud task starts in a clean environment, so anything needing persistent messaging, task chaining, or storage between runs still needs another solution.
Try it yourself with Claude Code
Set up a nightly scheduled task that scans [folders, repos, or notes] for the day's work, writes a short retrospective of what changed, and assembles a morning briefing saved to [file path or location]. The briefing should cover [what you want: open tasks, blockers, priorities] and fit on one page. Run it once now so I can check the output before you schedule it.