Multi-Agent Orchestration in OpenClaw: Centralize Rules, Spawn Sub-Agents
An OpenClaw user shares their evolution from isolated per-agent workspaces to a centralized orchestration pattern. Initially, they created separate agents—each with its own workspace-*—for use cases like System Administrator, Family Agent, Corporate Assistant, and Sports League Management. When developing a skill (e.g., a team-roster skill for the Sports agent), they would chat directly with that agent.
The pain point: when a cross-cutting rule emerged (e.g., “always persist structured data like points scores or spending ledgers in .JSON files”), they had to manually copy the instruction into every agent’s workspace. The solution was to promote a single “main agent” as the orchestrator. Now, the main agent holds all architectural rules (like the .JSON convention) and spawns sub-agents on demand to build tools. For example, to build a spending tracker for the Corporate agent, the user describes requirements to the main agent, which then ensures the skill built in the sub-agent’s workspace follows the central rules—no more duplication.
The user admits this pattern “now seems obvious” in hindsight, but notes that initially they were unsure whether the recommended “main agent orchestrates sub agents” pattern applied to agent-to-agent building scenarios.
📖 Read the full source: r/openclaw
👀 See Also
Silent Success: One Dev's Approach to Cron Job Alerting
A developer on r/openclaw stops sending success notifications for healthy cron runs, alerting only on auth failures, state corruption, or repeated failures.
Stop using Claude as an expensive autocomplete — build an SDR system with role definitions, memory files, and refinement rituals
A Reddit post argues that most sales teams use Claude as a 'chatbot' rather than a system. The fix: define a role, maintain a memory file with ICP/tone/learnings, and run a weekly refinement ritual to compound output quality.
7 MCP Gateway Bugs: Session Leaks, Dead SSE, and OAuth in Gateway Mode
A Reddit post details seven real-world MCP gateway bugs — session state leaking across clients, silent SSE disconnections, OAuth failures in gateway mode, and more — with fixes based on boring infra, not better prompts.
3 weeks of OpenClaw: token costs, loops, and compaction — lessons from the trenches
After burning tokens on heartbeat checks with Opus, fighting agent loops, and losing context to compaction, a Reddit user shares the hard-won fixes: use cheaper models for trivial tasks, write anti-loop rules, and save decision logs.