Work in lanes
Put each task in its own git worktree so agents do not collide with your main checkout or each other.
Talk to agents
Start lane-scoped chats with Claude, Codex, Cursor, or OpenCode and let agents edit, test, commit, and explain.
Review before merge
Use Files, PRs, Graph, and History to inspect diffs, CI, conflicts, proof, and session transcripts.
The usual loop
Open a repository
ADE creates local project state under
.ade/ and leaves your source tree under Git’s control.Create a lane for the task
A lane is an isolated branch and worktree. Use one lane per feature, fix, experiment, or PR.
Run an agent or a terminal
Ask for a targeted change in chat, launch an interactive shell, or hand larger coordination to the CTO and workers.
Inspect the result
Review changed files, terminal output, tests, PR state, and proof artifacts from one place.
App map
| Surface | Use it for |
|---|---|
| Run | Start dev processes, run tests, and see project health. |
| Lanes | Create, inspect, stack, archive, and clean up isolated worktrees. |
| Work | Manage chats, terminals, and CLI sessions across lanes. |
| Files | Read diffs, edit files, stage changes, and resolve conflicts. |
| Graph | See lane topology, PR links, stack relationships, and merge risk. |
| PRs | Create and review GitHub PRs, read CI, and manage stacked work. |
| History | Search the record of sessions, commits, PR activity, and checkpoints. |
| CTO | Ask project-level questions, delegate work, and manage worker agents. |
| Settings | Configure providers, GitHub, Linear, permissions, mobile, and usage. |
Quickstart
Follow the shortest path to a working agent.
Key concepts
Learn the product vocabulary before going deeper.