Multiple workspaces

Split work across agents only when the tasks are genuinely independent. Each agent should get its own workspace so context and file writes do not overlap.

When to split

Good candidates:

• Independent modules or packages
• Research tasks that do not write files
• Parallel test-fix loops on separate suites

Avoid splitting when agents would edit the same files. Conflicts should be surfaced for review, not merged automatically.

Keep review together

A workspace is the unit of context and review. Keep each run’s diff attached to its workspace, then review the results side by side before applying anything.

Parallel workspace execution is still in development. The current preview starts one run per workspace.