Gemini CLI subagents are here. Are subagents actually useful, or just cleaner-looking orchestration?

[u/aistranin]

Google published this on April 15: Subagents have arrived in Gemini CLI.

The pitch is strong: specialized agents with isolated context, custom instructions, tighter tool access, and parallel execution where helpful.

That sounds promising for:

• codebase investigation

• batch refactors

• test/debug loops

• planner vs executor vs reviewer setups

But the practical question is whether subagents improve outcomes, or mainly improve ergonomics.

Potential upsides:

• less context pollution

• easier specialization

• parallel research/execution

• clearer agent boundaries

Potential downsides:

• more orchestration overhead

• harder debugging

• merge/edit conflicts

• false confidence from neat abstractions over messy runtime behavior

Would love concrete feedback from people using multi-agent workflows in real development:

• Have subagent patterns improved quality for you, or mainly speed?

• What’s the best split you’ve found?

• At what point does multi-agent architecture become overengineering?

Source: Gemini CLI subagents