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.
Labels
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.
The author uses Claude Code cloud scheduled tasks for nightly pipelines that scan work, generate retrospectives, and assemble morning briefings.
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.
The author uses Claude Code cloud scheduled tasks for nightly pipelines that scan work, generate retrospectives, and assemble morning briefings.
The “Material” label failed its quality check and is not used for selection.
Details
- Agents
- Claude Code
- Source
- Source date
- Apr 11, 2026
- Accounts
- 1
- In registry since
- Oct 12, 2026