Dispatching Parallel Agents

Delegate one agent per independent problem domain, with isolated context. Construct exactly the context each agent needs; agents should never inherit your session's context or history. Keep coordination in the controller.

Eligibility

Use parallel agents when all of these hold:

• There are at least two tasks with separate outcomes: investigations, reviews, or fixes.
• Each task can be understood and completed without another task's result. Investigate related failures together until their dependencies are understood.
• Agents have separate write ownership and can work without interfering through shared state. Check files, fixtures, databases, generated artifacts, and the Git index, as well as other shared resources.

If a task needs full system context, narrow it first. Run dependent tasks sequentially. Shared read-only context is safe; shared mutations need a single owner.

Procedure

1. Partition

Group work by independent domain and assign ownership of files and resources. Keep shared integration changes with the controller or a designated owner. For example, tool approval, batch completion, and abort failures may be separate domains once their dependencies are checked.