Agent Swarm Spawner FAQs

Question 1

What is the benefit of spawning subagents?

Accepted Answer

Subagents provide context isolation, preventing your main conversation from becoming cluttered. They also allow for parallelization of tasks and cost optimization by using smaller models for simpler objectives.

Question 2

Is there a limit to how many subagents can be spawned?

Accepted Answer

While you can spawn up to 5 parallel subagents for independent tasks, it is recommended to avoid spawning subagents for one-liner tasks to prevent unnecessary coordination overhead.

Question 3

What information do subagents receive?

Accepted Answer

Subagents receive the specific prompt provided during spawning, global agent rules, and access to the same tools as the parent, but they do not see the parent's full conversation history.

Question 4

How does model selection work for subagents?

Accepted Answer

The system follows a hierarchy where trivial or simple tasks use Haiku, medium-to-complex tasks use Sonnet, and only the orchestrator or very complex tasks use Opus. Agents can self-downgrade to save costs.

Question 5

Can subagents perform git operations?

Accepted Answer

Yes, there is a specialized git-agent subagent type designed specifically for handling git operations using the Haiku model for maximum efficiency.

Agent Swarm Spawner

About

Key Features

Use Cases

Agent Swarm Spawner

About

Key Features

Use Cases