Hacking Multi-Agent Orchestration into OpenClaw: A Developer's Experience
A developer shared their experience modifying OpenClaw to implement true multi-agent orchestration after discovering that agents were pretending to collaborate without actually calling each other.
The Problem: Fake Collaboration
The developer initially set up multiple agents (PM, planner, backend, frontend, designer) with different assigned models, expecting an orchestrator to coordinate them. While responses appeared structured with different sections and perspectives, log analysis revealed the PM agent was doing everything solo and faking the other agents' contributions. None of the other agents were actually called.
The core issue: OpenClaw treats each agent as an independent unit with no built-in way for one agent to spawn another, wait for results, and fold them back in.
The Solution: Core Runtime Modifications
To implement proper orchestration, the developer modified the core runtime (reply-Bm8VrLQh.js) to handle:
- Parent-child agent spawning via sessions_spawn / sessions_yield
- Subagent completion events bubbling up to parent
- Proper message assembly for the gateway and TUI
The sessions_yield implementation was particularly challenging, requiring about 90 minutes of continuous Codex assistance to get the async flow correct.
Results and Tradeoffs
After implementation:
- Agents now run on separate threads in parallel
- Results get aggregated by the orchestrator
- PM receives a consolidated report and formats the final output
- Each agent actually uses its assigned model (fixing a bug where they all defaulted to the base model)
Tradeoffs include:
- Full pipeline takes 30-60 seconds vs near-instant for single agent
- Cost was about $0.90 over two days of testing
- Memory sits around 10-16GB during active runs
Hardware and Initial Setup
The developer used an M4 Mac Mini (32GB) as a dedicated AI assistant for organizing messy notes and summarizing research. They initially tried running LLMs locally with a 30B model but found it painfully slow and switched to commercial APIs (OpenAI, Claude, Gemini) through OpenClaw.
Output quality with orchestration is still being evaluated. For simple tasks, a single agent is faster and cheaper, but for complex multi-step tasks, specialization may pay off with more tuning needed.
📖 Read the full source: r/openclaw
👀 See Also
Local Qwen3-0.6B INT8 as Embedding Backbone for AI Memory System
A developer implemented Qwen3-0.6B quantized to INT8 via ONNX Runtime as a local embedding model for an AI memory lifecycle system, achieving 12ms batch inference on CPU with 1024-dimensional vectors and cosine similarity thresholds of 0.75 for semantic relatedness.
Wildlife Rescuer Uses Claude AI for Baby Squirrel Care Book and Interactive Chat Bot
A wildlife rescuer with 38 years of experience is using Claude AI to refine a 300-page book on baby squirrel care and has coded an interactive chat bot named Hazel to assist other rescuers. The rescuer is now testing Claude's capabilities by having it track and journal the progress of a baby squirrel named Nova.
AI agent cost breakdown: $12 monthly with local models and cloud APIs
A developer ran an AI agent for a month using Mac Mini + Ollama for local models and cloud APIs, costing $12 total with 80% local usage at $0 and 20% cloud usage at ~$12. A single retry loop consumed $4.80 in 11 minutes, prompting circuit breaker implementation.
Claude AI Analysis Reveals 'You Refine to Avoid Finishing' Pattern in User Conversations
A user analyzed six months of Claude conversation exports cross-referenced with journal entries and sleep data, discovering a behavioral pattern where refinement serves as avoidance of completion. Claude identified specific instances like generating '20 unique textures' for a logo or refining song lyrics through 'multiple iterations' as examples.