Main Agent + Sub-Agent Task Routing
Roger_M_Taylor · x · 2026-07-19
This post discusses a main agent + sub-agent execution architecture: the main agent handles planning and decision-making, while delegating actual execution to sub-agents.
The core practices include:
- The main agent's effort isn't fixed; it dynamically switches between low / medium / high based on the task. It defaults to low or medium, reserving high only for multi-step judgments.
- Sub-agents don't inherit the main agent's reasoning level; their models are explicitly specified at generation time based on the task.
The author provides routing examples:
- Routine execution, drafting, formatting, and simple tweaks go to sonnet
- Harder execution, debugging, and tasks requiring deeper reasoning go to opus
- Design work goes to GPT 5.5, and coding goes to GPT 5.6
This concept can scale to a week-long campaign: the main agent defines the launch week's angle and pace, then delegates retrieval, drafting, polishing, and scheduling to multiple sub-agents. The accompanying image emphasizes cost: high-effort tasks consume tokens rapidly, so heavy reasoning should be reserved for tasks that truly warrant it.
More from coding & agent
- GPT-6 Astra beats Factorio with enemies in 44 in-game hours at ~$4,500 API cost — liminal_bardo · 2026-09-11
- 105 hidden bugs, 2 repos: DeepSeek V4.1 Flash fixes 24 at $1.80 vs Opus 5's 27 at $51.33 — ChartsJournalX · 2026-09-11
- Investment Analyst Asks How to Build a Claude-Based Diligence Agent Stack — Careless_Tie2286 · 2026-09-11
- Treating agents like 50 First Dates: a 3-layer context system so every conversation doesn't start from zero — evielync · 2026-09-11
- Running the Firefox MCP on Android via Termux, ngrok, and mcp-proxy — Nervous-Strain7544 · 2026-09-11
- SmolVM open-sources persistent computer infrastructure for agents that outlive chat sessions — aniketmaurya · 2026-09-11