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
Fixing OpenClaw Agent Autonomy Issues: Skill Files, Tool Selection, and Cron Setup
A developer shares solutions for OpenClaw agents that stop working autonomously after initial setup. Key fixes include using external skill files instead of chat instructions, replacing browser tools with API-based tools or Puppeteer scripts, and properly configuring cron jobs.
Using Claude to analyze writing patterns for better custom instructions
A Reddit user describes a method for creating more effective custom instructions by having Claude analyze 10 writing samples to identify concrete patterns like punctuation avoidance and analogy sources, rather than relying on subjective tone descriptions.
Practical techniques to reduce state drift in multi-step AI agents
A developer shares concrete methods to fix state drift in multi-agent workflows, including snapshot-based reads, append-only writes, and separating state from context. These approaches made runs reproducible and debugging traceable.
OpenClaw 3.22 Upgrade Checklist: Practical Steps from a Developer Who Got Burned
A developer shares specific upgrade steps for OpenClaw 3.22, including checking for deprecated environment variables, creating backups, running migration commands, and verifying plugin compatibility.