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.

Isolated code

Each worktree has its own files and branch.

Scoped sessions

Chats and terminals run in the selected lane.

Reviewable output

A lane can be committed, pushed, and turned into a PR.

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

1. Create

   Start from the default branch or from another lane when building stacked work.

2. Work

   Open chat, terminals, Files, or Run scoped to the lane.

3. Review

   Inspect the diff, tests, proof, History, and conflict risk.

4. Ship

   Commit, push, create a PR, merge, archive, or delete the lane.

Stacked lanes

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

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.

Create lanes

More detail on lane creation and cleanup.

Stacked PRs

Work with branch chains and reviewable stacks.