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
VPS vs Dedicated Machine: Where to Run OpenClaw
Running OmniCoder-9B locally with llama.cpp configuration details
A developer achieved 96.7% average HumanEval score with OmniCoder-9B on mid-range hardware using specific llama.cpp flags including --reasoning-budget 0 to disable chain-of-thought output. The setup used a Q6_K quantized model running on an RTX 3080 with 10GB VRAM.
Setting Up MCP Servers in llama-server Web UI: A Practical Guide
A Reddit user shares specific steps to configure MCP servers in llama-server's web UI, including installing uv, creating a config.json file with server definitions, running mcp-proxy, and modifying URLs for proper integration.
Building a serverless AI agent platform on AWS for $0.01/month with Claude Code
A developer built a complete AWS serverless platform running AI agents for approximately $0.01/month using Claude Code over 29 hours, eliminating expensive components like NAT Gateway ($32/month) and ALB ($18/month). The project includes 233 unit tests, 35 E2E tests, and deploys with a single cdk deploy command.