Parallel Agent Orchestration When launching multiple agents in parallel, follow this pattern to avoid context bloat. Core Principles 1. No TaskOutput calls TaskOutput returns full agent output, bloating context 2. Run in background Always use run in background: true 3. File based confirmation Agents write status to files, not return values 4. Append, don't overwrite Multiple agents can write to same status file Output Patterns Simple Confirmation (parallel batch work) For tasks where agents just need to confirm completion: Use to append (not which overwrites) Include timestamp for ordering One line per agent completion Check with: cat .claude/cache/<batch name status.txt Detailed Output (research/exploration) For tasks requiring detailed findings: Each agent gets own directory Full output preserved for later reading Status file still used for quick completion check Task Prompt Template Launching Pattern Monitoring Batch Size Max 15 agents per parallel batch Wait for batch to complete before launching next Use status file to track which completed DO Use run in background: true always Have agents write to status files Use append ( ) not overwrite ( ) Give each agent clear, self contained instructions Include all context in prompt (agents don't share memory) DON'T Call TaskOutput (bloats context) Return large outputs from agents Launch more than 15 at once Rely on agent return values for orchestration Example: Provider Backfill Check progress:

parallel-agents