OpenClaw Orchestrator Routing Issues: When Delegation Fails
The Problem: Unreliable Agent Delegation
A developer running OpenClaw with a hub-and-spoke multi-agent architecture is experiencing unreliable routing behavior from their main orchestrator. The orchestrator frequently attempts to handle requests directly instead of delegating them to the appropriate specialist sub-agent. According to the report, routing feels unreliable, with delegation working correctly only about 50-60% of the time.
Specific examples include: when asked about workouts, the orchestrator provides generic fitness advice instead of calling the training agent; when asked about weather, it answers from training data instead of calling the weather agent.
Current Setup Details
The developer's configuration includes:
- Main orchestrator handling user interaction
- 7 specialist sub-agents for: Gmail/Calendar/Drive, Todoist, personal training/Notion, grocery inventory, meal planning, weather, and train schedules
- Explicit routing table mapping request patterns to agent IDs
- Hard rule: "You are a ROUTER not a WORKER — if a request falls into any specialist's domain, you MUST delegate"
- Each specialist has its domain clearly defined
- Agent-to-agent communications enabled in configuration
- Orchestrator model: gpt-5.4 via openai-codex
Attempted Solutions
The developer has tried several approaches to fix the routing issue:
- Adding "NEVER" rules for each domain (e.g., NEVER answer email questions yourself, NEVER check weather yourself)
- Adding a "when in doubt, delegate" rule
- Making the routing table very explicit with example phrases
Key Questions from the Developer
The developer is seeking practical advice on several specific issues:
- Is there a known working prompt pattern to force reliable delegation in OpenClaw?
- Does the model choice for the orchestrator matter significantly? Should it be a stronger or weaker model?
- Is the routing table approach the right one, or is there a better way to structure this?
- Any experience with how OpenClaw's
subagents.allowAgentsconfig affects routing behavior?
The developer notes that individual agents work well once they receive requests, indicating the bottleneck is purely at the routing step.
📖 Read the full source: r/openclaw
👀 See Also
Financial Analyst Uses Claude Code to Build DCF Model Without Coding Experience
A financial analyst with no terminal experience used Claude Code to build a discounted cash flow model in 20-25 minutes instead of 1-2 days. The tool read financial files and generated a fully structured Excel model with working formulas after the user typed /dcf [company name].
OpenClaw Cost Optimization: How a Developer Fixed a $750 Mistake with Model Routing
A developer shares how switching all OpenClaw subagents to the free Hunter Alpha model on OpenRouter led to silent failures, including a video production agent that generated valid code but produced a 9-second silent black video. The solution involved implementing explicit model routing based on task requirements.
Developer Gives Claude Code Root Access, Flips Development Workflow
A developer gave Claude Code root access to their server, monitored all commands, and found it made calm, methodical changes that addressed root causes rather than just symptoms. This led to flipping their workflow to develop directly in a production-cloned environment.
Non-developer finds managed OpenClaw setup via MaxClaw on MiniMax Agent platform
A freelance marketing consultant with no coding background successfully deployed an AI agent using MaxClaw on the MiniMax Agent platform, avoiding Docker and API key management. The agent handles daily competitor monitoring, drafts social copy, and summarizes articles.