Subagents
Current Answer
No editorial synthesis yet — the evidence below is collected automatically from source labels. A current answer lands here once an editor approves one.
Evidence
Production agent velocity depends less on model swaps than on automating the developer loop: isolate parallel work, encode workflows as skills, connect tools, and keep humans as verifiers.
A fixed chain of specialist agents lost context and produced incoherent recommendations. The replacement separates deterministic detection, gives one agent end-to-end ownership, and uses subagents only for bounded investigations.
Vercel AI Gateway added Gemini 3.6 Flash for coding and web work and Gemini 3.5 Flash-Lite for scoped subagent tasks, both available through AI SDK model IDs.
Cursor’s SQLite experiment suggests swarm harness design can matter more than model mix: separate planner and worker contexts reduced coordination churn while cheaper workers handled most tokens.
Muse Spark 1.1 gives agent builders a 1M-token multimodal model with parallel tool calls, MCP support, and the option to run as a main agent or subagent.