> ## Documentation Index
> Fetch the complete documentation index at: https://ade-ac1c6011-ade-mobile-chat-stability-54bd7ef0.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Multi-agent setup

> Run several agents safely by giving each task its own lane and review path.

The safest multi-agent setup is simple: one lane per task, one clear goal per agent, and a review pass before merge.

## Recommended pattern

<Steps>
  <Step title="Split the work">
    Turn a large goal into small lane-sized tasks.
  </Step>

  <Step title="Create one lane per task">
    Name lanes after the outcome, not the agent.
  </Step>

  <Step title="Start one chat per lane">
    Keep each prompt scoped to that lane's goal.
  </Step>

  <Step title="Watch Work and Graph">
    Use Work for live sessions and Graph for branch relationships.
  </Step>

  <Step title="Review independently">
    Inspect each diff, run tests, and create PRs separately.
  </Step>
</Steps>

## Good task splits

| Goal                      | Better split                                                       |
| ------------------------- | ------------------------------------------------------------------ |
| "Improve onboarding"      | Copy fixes, provider validation, first-run UI, tests.              |
| "Fix checkout bugs"       | Repro failing case, patch backend, patch UI, add regression tests. |
| "Ship mobile sync polish" | Desktop status, iOS display, reconnect behavior, docs.             |

## Keep agents from colliding

* Do not send two agents into the same lane for unrelated work.
* Avoid broad prompts that invite repo-wide edits.
* Use stacked lanes when one task depends on another.
* Merge parent work before rebasing children when possible.
* Use History to understand what each session changed.

<CardGroup cols={2}>
  <Card title="Lanes" icon="code-branch" href="/lanes/overview">
    Isolate each task.
  </Card>

  <Card title="Workspace graph" icon="diagram-project" href="/tools/workspace-graph">
    See how parallel work relates.
  </Card>
</CardGroup>