Keep Subagents to 3 or 4 for Optimal Performance
jasondeanlee · x · 2026-07-14
The author argues that in their use cases, 3 to 4 subagents are generally sufficient, as adding more rarely yields noticeable performance gains. Instead, excessive subagents can trigger memory pressure and swapping on macOS, especially when running multiple sessions simultaneously.
They also shared troubleshooting tips: after mapping the entire process tree, they cleared out numerous redundant background items, including stale dev servers, duplicate MCP servers, headless browsers, login items, VPN/network extensions, browser helpers, and various updaters. Post-cleanup and reboot, lag during prolonged multi-agent workloads was significantly reduced.
More from coding & agent
- Google launches Gemini 3.5 Flash Cyber for CodeMender, with limited access for governments — GoogleAI · 2026-07-22
- Cursor doubles usage limits across all plans for Grok, Composer and new models — XFreeze · 2026-07-22
- Video-based proof of work is emerging as a feedback layer for coding agents — Vjeux · 2026-07-22
- Salesforce open-sources MCP+ to filter tool output before it reaches agents — msrivastav13 · 2026-07-22
- Anaconda acquires Kilo Code to expand into agentic software development — anacondainc · 2026-07-22
- Poolside’s laguna s 2.1 claims 118B MoE, 1M context, and 78.5% on SWE-bench Multilingual — ben_burtenshaw · 2026-07-22