> ## 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.

# Lanes

> Use lanes to isolate parallel agent work in separate Git worktrees.

A lane is one task's workspace. It has its own branch, worktree, sessions, diff, and PR link. Lanes let several agents work in the same repository without writing over each other.

<CardGroup cols={3}>
  <Card title="Isolated code" icon="shield">
    Each worktree has its own files and branch.
  </Card>

  <Card title="Scoped sessions" icon="comments">
    Chats and terminals run in the selected lane.
  </Card>

  <Card title="Reviewable output" icon="code-pull-request">
    A lane can be committed, pushed, and turned into a PR.
  </Card>
</CardGroup>

## Lane types

| Type         | Use it when                                                                                                     |
| ------------ | --------------------------------------------------------------------------------------------------------------- |
| **Primary**  | You need to inspect or run commands in the repository root. Be careful: agents write to the main checkout here. |
| **Worktree** | You are doing normal agent work. This is the default and safest choice.                                         |
| **Attached** | You already have an external worktree and want ADE to track it.                                                 |

## Common actions

<Steps>
  <Step title="Create">
    Start from the default branch or from another lane when building stacked work.
  </Step>

  <Step title="Work">
    Open chat, terminals, Files, or Run scoped to the lane.
  </Step>

  <Step title="Review">
    Inspect the diff, tests, proof, History, and conflict risk.
  </Step>

  <Step title="Ship">
    Commit, push, create a PR, merge, archive, or delete the lane.
  </Step>
</Steps>

## Stacked lanes

A stacked lane is based on another lane instead of `main`.

```text theme={null}
main
  auth-base
    auth-ui
      auth-tests
```

Use stacks when one large change is easier to review as several smaller PRs. ADE keeps the relationship visible in Lanes, Graph, and PRs.

## Cleanup

Archive lanes you may need later. Delete lanes when the branch is merged or abandoned and you are done with the worktree. ADE asks for confirmation before removing managed worktrees.

<CardGroup cols={2}>
  <Card title="Create lanes" icon="plus" href="/lanes/creating">
    More detail on lane creation and cleanup.
  </Card>

  <Card title="Stacked PRs" icon="layer-group" href="/lanes/stacks">
    Work with branch chains and reviewable stacks.
  </Card>
</CardGroup>