Feature: Persistent cron jobs via background daemon
Feature Request
CronCreate is great — scheduling recurring prompts within a session is a powerful workflow. But jobs die when the session exits, which limits the feature to long-running sessions only.
Proposed: Persistent cron via a background daemon
A lightweight daemon service that:
- Persists jobs to disk (SQLite, JSON, etc.) so they survive session exits and reboots
- Runs independently of any active Claude Code session
- Spawns headless Claude Code sessions when a job fires (similar to
claude -p "prompt") - Integrates with existing CronCreate/CronList/CronDelete — same UX, just persistent
Real-world use case: Automated codebase garbage collection
I set up a daily cron job to pay down tech debt automatically:
/loop once per day run /simplify pay down tech debt over the last two
implemented specs. do it as an intermediary spec implemented with the
SPIR protocol under codev/garbage-collection/
This schedules a daily /simplify pass that:
- Launches 3 parallel review agents (code reuse, quality, efficiency)
- Aggregates findings into a prioritized list
- Creates a spec + plan under a garbage-collection directory
- Implements the fixes autonomously
- Runs the full test suite to verify
The problem: This only works while my session is open. I want this running every night regardless of whether I have Claude Code open. A daemon would make this "set and forget" — like a CI job but for continuous codebase health.
Suggested UX
# Current (session-only, already works)
/loop 1d /simplify ...
# Proposed (persistent, survives exit)
/loop 1d --persist /simplify ...
# Or a separate command
/cron create "0 0 * * *" /simplify ...
# Manage persistent jobs from any session
/cron list
/cron delete <id>
The daemon could also serve other use cases:
- Nightly test runs with failure triage
- Periodic dependency update checks
- Scheduled PR review sweeps
- Monitoring/alerting on codebase metrics
Love the direction CronCreate is going — persistent scheduling would unlock a whole new class of autonomous workflows.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗