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
OpenClaw: Your Ultimate Quick Reference Cheatsheet
Dive into the nitty-gritty of OpenClaw with our handy reference cheatsheet. Extract critical features and functionalities to streamline your AI coding experience.
Using the Dispatcher Pattern to Reduce Claude API Costs by 95%
A developer reduced their Claude API costs from $800-$2,000/month to about $215/month by implementing a dispatcher pattern that delegates heavy work to Claude Code CLI on a Claude Max subscription, while using minimal API tokens for orchestration.
Claude for Motion Graphics: Prompt Patterns That Produce Animated HTML Visuals You Can Capture as Video
A r/ClaudeAI user shares a reliable prompt structure for generating animated motion graphics and interactive charts as HTML widgets from Claude, then capturing them as MP4 with Playwright + ffmpeg.
OpenClaw Memory Plugin Analysis: Lossless Claw + LanceDB Recommended
A developer tested OpenClaw memory plugins and found that the default setup causes token bloat, while Lossless Claw paired with LanceDB provides optimal performance for maintaining agent context without high costs.