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
Fully Automated Product Tutorial Videos: Claude + Playwright + Magic Hour + Remotion
A developer built a zero-human pipeline that turns a feature URL into a finished tutorial video using Claude for script/orchestration, Playwright for screen recording, Magic Hour API for face swap/lip sync, and Remotion for editing.
Thread per Project, File for the Long Stuff: How I Organize My OpenClaw Agent Home
An OpenClaw user rebuilds their agent home three times, landing on Discord with a thread-per-project structure and a file-baton workaround for long messages.
Claude Built a Skeuomorphic Keyboard Simulator in One Session — Public Transcripts, CORS Proxied Unsplash Backgrounds
A single Claude session produced a skeuomorphic typing app with public transcript, hidden input for native shortcut handling, SVG keys from Figma, and CORS-proxied Unsplash backgrounds served as WebP.
Multi-agent security review running daily in production: architecture and findings
ultrathink.art runs 6+ AI agents in production including a dedicated security agent that performs daily vulnerability checks against a structured checklist, files findings as prioritized tasks, and has a coding agent fix them automatically.