Parallel tasks

Parallel work in LegionCode means running multiple independent tasks at the same time. Each task has its own conversation, workspace, event stream, and review state.

What parallel means

Two browser conversations can execute concurrently when each maps to a separate run. They may start from the same repository and branch, but they do not share a writable workspace.

Parallel execution does not mean multiple agents collaboratively editing one working tree. Coordination happens when a developer reviews and reconciles the resulting changes.

Choose good boundaries

Good parallel tasks have low file overlap:

• one task updates provider validation while another updates documentation;
• one task fixes a UI state while another adds an isolated API contract test;
• one task investigates a failure while another implements an unrelated feature.

Avoid running two tasks that both rewrite the same component, migration, or shared contract. Isolation prevents filesystem conflicts, but it cannot make conflicting product decisions compatible.

Reconcile results

Review every run independently. Before merging more than one result:

1. compare changed paths for overlap;
2. choose a merge order;
3. update later work against the accepted base;
4. rerun affected tests after reconciliation.