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

Using Claude Code to Build a Drupal Site with Custom Twig Templates
A developer used Claude Code to create a Drupal website with custom Twig templates and raw HTML, bypassing traditional Drupal theming. They employed ddev for local development and specific commands to configure content types, views, and taxonomies.

VPS vs Mac Mini for OpenCLAW: Why a $5 VPS beats a $599 Mac Mini for production agents
OpenCLAW creator Peter Steinberger told users to stop buying Mac Minis and sponsor devs instead. A €5 VPS with 2 vCPUs and 4GB RAM handles continuous OpenCLAW workloads at 3-8% CPU, while a Mac Mini costs $599+ plus $10-15/mo electricity.

User Creates HTML Converter for Claude Chat Exports Using Claude Itself
A non-coder used Claude to build a converter that transforms Claude's native JSON chat exports into readable HTML with color-coded messages, collapsible conversations, and organization by date and time.

OpenClaw user builds character chat app with agentic coding approach
A self-described non-technical OpenClaw user developed a working character chat application in 7 days using agentic coding, noting that their role shifted to reviewing AI-generated work rather than traditional programming.