Lane
One isolated branch and worktree per task.
Work
The place where chats, terminals, and CLI sessions run.
Agent chat
A lane-scoped conversation that can edit, run, test, and commit.
CTO
A project-level agent for planning and delegation.
Worker
A scoped agent assigned to a specific job.
Proof
Evidence captured during work.
PR flow
GitHub review tied back to lanes.
History
Searchable record of sessions, commits, and checkpoints.
iOS companion
Phone pairing for updates and remote follow-up.
Lane
A lane is ADE’s unit of parallel work. It is a Git branch in an isolated worktree, usually under.ade/worktrees/<lane-name>/. Agents, terminals, diffs, tests, and PRs are scoped to that lane.
Use one lane for one feature, bug fix, experiment, or review thread. If the work grows, split it into another lane or stack a child lane on top of it.
Work
Work is where active execution happens. A Work session can be a chat, a terminal, a provider CLI, or a managed process. ADE keeps these sessions visible and attributable so you can answer “what is running, where, and why?”Agent chat
Agent chat is a conversation with a coding agent inside a lane. The agent can read files, edit files, run shell commands, inspect diffs, create commits, and help open PRs. Tool calls and results stay in the transcript. Provider support depends on what you have configured, but the main paths are Claude, Codex, Cursor, and OpenCode.CTO
The CTO is a project-scoped agent. Use it for planning, summarizing project state, coordinating workers, routing Linear issues, and deciding how to split work. It is not the fastest way to make a tiny edit; lane chat is usually better for that.Worker
A worker is a scoped agent identity the CTO can use for delegated work. Workers have roles, model settings, budget controls, and activity history. They are useful when you want repeatable responsibility, such as testing, review, or implementation in a specific area.Proof
Proof is intentional evidence: screenshots, recordings, browser traces, console logs, or verification notes captured during work. Proof artifacts can be tied to a chat session, lane, PR, or Linear issue.PR flow
ADE links lanes to GitHub PRs. From that link, ADE can show review state, CI, changed files, comments, merge risk, and stacked PR relationships. The point is simple: review the agent’s work before it lands.History
History is the searchable project record. It includes chats, terminal sessions, commits, PR events, lane changes, and checkpoints. Use it when you need to recover context or explain what happened.iOS companion
The iOS app pairs with the desktop runtime. It can mirror useful project state, receive push notifications, and let you follow work from your phone. The phone does not run agents; your Mac remains the execution host.Local project state
ADE stores project data in.ade/ inside your repository. That directory contains the local database, worktrees, artifacts, caches, and machine-specific state. Keep it out of Git unless a page explicitly tells you a file is safe to share.