OpenClaw setup evolution: from overconfiguration to practical multi-agent system
A developer documented their OpenClaw evolution after three reinstalls, moving from experimental overconfiguration to a practical multi-agent system focused on continuity and specialization.
Setup details
Primary installation runs on Mac mini M2 with these specialized agents:
- Main → life and daily tasks
- Cultivator → plants
- Tutor → studies
- Nutritionist → diet
- Trainer → workouts
A separate agent for research/testing runs on Hetzner (~7€/month), with plans to test RunPod with an uncensored local model as a separate lab.
Model usage
General models:
- Primary: openai-codex/gpt-5.3-codex
- Fallback #1: anthropic/claude-sonnet-4-6
- Fallback #2: google-gemini-cli/gemini-3-flash-preview
For cultivator agent:
- Primary: anthropic/claude-sonnet-4-6
- Fallback #1: google-gemini-cli/gemini-3-flash-preview
Approximate monthly cost: ~50€ (Codex + Claude + Gemini), though the system could function with only Codex (~25€/month).
Key working components
1) Layered memory system:
- Daily → memory/YYYY-MM-DD.md
- Weekly → memory/weekly/YYYY-WW.md
- Long-term → MEMORY.md
The key: not mixing daily with durable content.
2) Promotion with criteria: Only content with real value (durability, impact, frequency, actionability, and risk of forgetting) moves to MEMORY.md.
3) Traceability: Important items include source (path#line) to avoid "invented memory."
4) Semantic search: Uses local indexing with QMD backend for semantic retrieval + text fallback, with automatic updates (interval + debounce). This enables context recovery by meaning, not just exact words.
5) Multi-agent integration: Each agent handles its own closures (daily/weekly), with the main agent integrating state and maintaining cross-cutting continuity. Result: less manual recapping and less friction when resuming.
6) Night automation: Automatic closures between 23:00–00:00 for consolidated morning results.
Conclusion
<The developer sought continuity + specialization rather than business setups or web scraping. When configured with this intention, OpenClaw changes completely.
📖 Read the full source: r/openclaw
👀 See Also
Corporate Developer's Claude Workflow for Backend Development
A backend developer at a large US finance company shares their Claude workflow: providing detailed task descriptions with specs and internal documents, using Claude to create a working markdown document, then employing a codeReviewing agent with organizational style guidelines.
Claude AI Analysis Reveals 'You Refine to Avoid Finishing' Pattern in User Conversations
A user analyzed six months of Claude conversation exports cross-referenced with journal entries and sleep data, discovering a behavioral pattern where refinement serves as avoidance of completion. Claude identified specific instances like generating '20 unique textures' for a logo or refining song lyrics through 'multiple iterations' as examples.
OpenClaw and Remotion Pipeline for Automated Video Editing
A developer describes an agent-driven workflow using OpenClaw for orchestration and Remotion for rendering to automatically create 20 Reels from 400+ clips, with filtering, JSON-defined montages, and batch processing.
Building a Personal AI Agent with Claude Code: Lessons from 6 Months of Wiz
A developer shares their experience building Wiz, a personal AI agent on Claude Code that handles morning reports, evening summaries, and inbox triage. The post details 9 mistakes made during development, including starting with overly ambitious goals and letting Claude generate core instructions without review.