Building a Self-Improving Dream Cycle with Cron Jobs and Claude
A developer on r/openclaw shared their implementation of a self-improving dream cycle using cron jobs and Claude Sonnet. The system runs autonomously each night to research, reflect, and propose improvements based on identified weaknesses.
Architecture and Setup
The system uses two cron jobs running back-to-back:
- 10:30 PM: Dream Cycle - Research and reflection
- 11:00 PM: Nightly Review - Scoring and planning
Dream Cycle Phases
The 10:30 PM job executes four phases:
- SCAN: Web search across arXiv, GitHub trending, r/openclaw, and r/LocalLLaMA for new tools, papers, and techniques related to current projects
- REFLECT: Reads daily logs and recent review scores to identify specific weaknesses (e.g., identified revenue as weakest pillar - $0 after 11 days despite 4 shipped products)
- DEEP RESEARCH: Picks 1-3 findings most relevant to the weakest area, fetches and reads them, and applies them to the specific situation
- PROPOSE: Writes concrete proposals with effort estimates and expected impact, tagging revenue/distribution findings as PRIORITY
Nightly Review Process
The 11:00 PM job reads the dream cycle output, scores the day 1-5, incorporates findings into tomorrow's plan, and saves lessons to a tacit knowledge file.
Night One Results
The first run found 6 things, with three being actionable:
- A UK government study analyzing 177,000 AI agent tools found that 'action tools' (tools that modify external environments) grew from 27% to 65% of usage. This led to a proposal to change product positioning from generic 'discover and reply' to 'AI agent that finds your customers.'
- A r/LocalLLaMA thread revealed skepticism about AI agents genuinely self-improving, identifying a content opportunity since this system runs autonomously and connects research to specific weaknesses.
- A code review benchmark paper prompted a proposal to add a lightweight review gate before deploys since the builder cron ships code without review.
Self-Improvement Mechanism
The system already improves its own research methodology based on meta-notes from night one:
- 'Reddit fetch often returns login walls - use old.reddit.com next time'
- 'GitHub trending search returned zero results - try different query format'
- 'Add Hacker News scan next cycle'
Costs run approximately $0.30-0.50/night using Claude Sonnet. The developer noted they would use model routing in future iterations - cheap model (Haiku) for broad scanning and expensive model (Opus) only for judging/proposing phases to further reduce costs.
📖 Read the full source: r/openclaw
👀 See Also
Snip tool enables visual communication with AI coding agents
Snip is a free tool that lets developers screenshot, annotate, and draw to show AI agents what they mean visually, while agents can generate diagrams or load images directly through CLI or MCP. Currently runs on Apple Silicon Macs with Mermaid diagram support and HTML support in progress.
Rails-AI-Context Gem Provides Claude Code with Complete Rails App Model via MCP
The rails-ai-context gem auto-introspects Rails applications and exposes 39 tools via MCP, allowing Claude Code to query specific app details like schema with encrypted columns, model associations, routes, Stimulus wiring, and Turbo mappings instead of reading entire files.
Visdiff: Visual Feedback Loop for Claude's Frontend Code Generation
Visdiff addresses the visual accuracy gap in Claude's frontend code generation by comparing rendered output pixel-by-pixel with Figma designs and feeding differences back into the loop until they match.
Collaborate: A Claude Code Skill for Structured, Asynchronous Document Writing with Multi-Agent Handoffs
A Claude Code skill called 'collaborate' enables multi-contributor document writing where each participant gets a plain‑English briefing from Claude on previous changes, reasoning, and next tasks, with support for parallel sections, structured critique, and Slack/Signal notifications.