OpenClaw Project Operating System: Multi-Project Management Framework
Core Problem and Solution
The OpenClaw Project Operating System addresses execution failures and inconsistencies in multi-project environments. The main issue was agents doing predictable work that should be handled by tools, leading to wasted tokens, context pollution, instability, and inconsistent execution.
The core shift: "Agents should not do predictable work. Tools should." Agents were doing repetitive work like babysitting processes, repeatedly summarizing, checking status loops, and managing state manually. Now tools and scripts handle all predictable tasks, cron runs everything automatically, and agents are used only for planning, debugging, and decision-making.
System Architecture
Core System Rules:
- Agents think. Tools do. Cron runs code.
- Every project is isolated with required structure: /project_name/ PROJECT.md SKILL.md /state/ /chat/ /daily/ /scripts/ /logs/ /backups/ /archive/ /cleanup_queue/
- File-first memory: Memory is markdown docs, JSON state, logs, and summaries (chats are NOT memory)
- Backup-first (mandatory): Before any change, backup first, version files, allow rollback
- Pull before push (critical): Before updating servers, websites, or remote systems, you must: 1. pull 2. compare 3. backup 4. then push
- No instant deletion: Move files to archive/ or cleanup_queue/, delete later via cron
- Explain changes: If changing anything, explain problem, solution, benefit, and confirm backup
Automation System
Cron runs scripts, jobs, and deterministic tasks but NOT freeform agents or reasoning loops.
Required Cron Jobs:
- Project Discovery: Find all projects, validate structure, build registry
- 6-Hour Summarizer (local model): Summarize project, keep last 10 messages, archive rest, fresh context every run
- Daily Planner: Log daily work, track blockers, track decisions
- Health Check: Detect stale projects, failed jobs, missing updates
- Backup/Checkpoint: Version files, snapshot state
- Weekly Cleanup: Remove old files only if safe, require checkpoint
- Cron Audit: Detect missed jobs, failures
- Scheduled Posting: Use JSON + tools, no agents
- Remote Sync: Pull before updating, compare versions
- Morning Report: Summarize all projects, prepare for agent review
Summarization System
Every 6 hours: Read project logs, summarize, update state, keep only last 10 messages, archive rest.
📖 Read the full source: r/openclaw
👀 See Also
How 40 Prompt Revisions Turned Claude AI Summaries Into a Product: A Tutoring Platform Case Study ($19K MRR)
A tutoring platform with $19K MRR iterated their Claude-generated session summary prompt 40+ times over 12 months. The journey from vague v1 to personalized v40 shows how prompt engineering transforms a feature into a product.
Making an MCP Server Install Itself: Three Hosts, Three Mechanisms, Gotchas
A deep dive into programmatically installing MCP servers across VS Code, Cursor, and Claude Code — covering APIs, file writes, and edge cases like malformed JSON, atomic writes, and idempotent updates.
OpenClaw Failure Patterns: 42 Real Incidents in 28 Days
A developer running OpenClaw daily documented 42 specific failures across eight categories, including AI hallucinations, authentication breakdowns, and automation that costs more time than it saves. The source provides concrete examples like Google OAuth 7-day token expiration and Opus 4.6 adding unwanted metadata to files.
Practical Claude Code Workflow for Development Teams
A Reddit user shares their internal presentation on Claude Code best practices, including model selection, structured workflows, and specific prompt techniques to improve output quality.