dispatching-parallel-agents

Topics in the source

• Dispatching Parallel Agents
• Overview
• When to Use
• The Pattern
• 1. Identify Independent Domains
• 2. Create Focused Agent Tasks
• 3. Dispatch in Parallel
• 4. Review and Integrate

You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work. When you have multiple unrelated failures (different test files, different subsystems, different bugs), investigating them sequentially wastes time. Each investigation is independent and can happen in parallel. Core principle: Dispatch one agent per independent problem domain. Let them work concurrently. Use when: 3+ test files failing with different root causes Multiple subsystems broken independently Each problem can be understood without context from others No shared state between investigations Don't use when: Failures are related (fix one might fix others) Need to understand full system state Agents would interfere with each other Group failures by what's broken: File A tests: Tool approval flow File B tests: Batch completion behavior File C tests: Abort functionality Each domain is independent - fixing tool approval doesn't affect abort tests. Each

This is an excerpt. Refer to the complete source and its current requirements.