Skip to main content
Create a lane whenever a task deserves its own branch and review path.

Create a lane

1

Open Lanes

Click New lane from the Lanes view.
2

Name the task

Use a short outcome name like fix-auth-redirect or add-health-endpoint.
3

Choose the source

Start from the primary branch, an existing branch, or another lane when creating stacked work.
4

Create

ADE creates the worktree and shows the lane in the list.

Attach an existing worktree

If you already created a Git worktree outside ADE, attach it from the lane actions. ADE tracks the lane but does not move the directory.

Rename, archive, or delete

ActionUse it when
RenameThe task name is unclear. This changes ADE metadata, not necessarily the Git branch name.
ArchiveThe work may be useful later but should leave the active list.
DeleteThe worktree is no longer needed. Commit or stash anything important first.
Deleting a managed worktree can remove uncommitted changes. ADE warns before destructive cleanup, but review the lane status first.

Good cleanup habits

  • Archive stalled experiments instead of keeping every lane active.
  • Delete lanes after their PRs merge and follow-up work is complete.
  • Keep lane names tied to outcomes, not model names.
  • Use History if you need to find what happened in a deleted or archived lane.