Agents fly the legs.
You land the change.
Atlas ADE sets up Claude Code and Codex in any repository, keeps a generated chart of your code, and drives every change through one short loop. It stops only when it needs you, with the next command already on screen.
$ ade card add "greet takes a name" \ --path src/greet.py --done "greet(\"Ada\") says hello"c1 next: ade loop c1$ ade loop c1lane advance lane ~/.ade-work/61eadb80/c1build advance built with claudereview advance light review approvedtest advance passed: tests/test_greet.pyland done landed c8b7669b5c$
Scripts fly the route. A model is on call.
Routine legs are scripts and wake nobody. A model is woken to build, to review, and when a stop needs judgement, and you only when the call is yours. Any stop goes into a hold, and the card rejoins the course where it left it.
- 01 · pickThe next cardThe conductor takes the oldest open card, or several at once that the graph keeps apart, or you name one, and notes anything that moved under its paths since it was written.
- 02 · laneIts own worktreeEach card gets an isolated git worktree, so builders never collide on your checkout.
- 03 · buildEither engineClaude Code or Codex makes the smallest change that meets the card's done line.
- 04 · reviewA patch, not a listNone for prose, one light round for code. The reviewer hands back a fix, applied once.
- 05 · testWhat the change reachesTests are picked from the graph. An unknown path runs a small critical set, never everything.
- 06 · landOne verdictMerge, one outcome record, and any reds carried to a single residuals card.
- 07 · holdRecover and rejoinEvery stop is routed by one table: retry a blip, wait on a condition, wake a model to judge, or park it for you. Rerunning resumes where it stopped.
Think of a small aircraft.
Every part of Atlas ADE has one job, the way every instrument on a panel does. Nothing flies the aircraft except the loop.
Every change has a blast radius.
ADE keeps a chart of your code: which files call which, which tests reach them and which decisions govern them. Pick a waypoint to see what an edit there would touch, and the briefing an agent is handed the moment it arrives. The project below is invented; your chart is generated from your own code.
Every session picks up where the last one left off.
A long chat drifts and a new one forgets. So ADE does not rely on either: when a session opens, it writes the agent's working context fresh from the project's records: open cards and their next command, the decisions in force, questions waiting on you, recent landings and an outline of the graph. The whole thing is budgeted: about 200 tokens on a new project and 550 on ADE itself, against 20,000. Long command output stays out of context too: ade q keeps it in a store the agent pages through.
# ADE handover: builder Builds one card in its lane: the smallest change that meets the card's done line. ## Open cards - c1 greet takes a name [mp/greet.py, tests/test_greet.py] state: not started; next: `ade loop c1` - c2 log every greeting [mp/greet.py] done: greet writes one line per call state: not started; next: `ade loop c2` ## Graph (4 files; each edit is briefed from it) - mp/greet.py: the starter's one function (1 callers) ## Budgets core lines 14 / 20000 ok hooks 5 / 5 ok refusal codes 41 / 50 ok ~193 tokens (budget 20000) · empty sections and c1's done line trimmed
Small on purpose.
Budgets are the only standing gates, and every merge prints where the kit stands against them. Your telemetry stays on your machine.
PLACARDLIMIT
Core code~20,000 lines
Warm-up per role~20,000 tokens
Hooks≤ 5
Refusal codes, each with a cure≤ ~50
Whole test suite< 5 min
Get Atlas ADE
Start a new project on it in an empty folder, or install it into a repository you already have. One command either way, with a dry-run diff first and a clean uninstall.
$ ade init --dry-run $ ade init $ ade loop c1
- The
adeCLI for macOS, Windows and Linux - Claude Code and Codex from one roster
- Python and TypeScript starters, Orca or CLI-only cockpit
- The kit as it is when you buy it
- Everything in the kit
- Every kit release for 12 months
- One-off payment, no subscription
Bought the £14.99 kit? Add 12 months of updates for £12.99 from your account, whenever you like. VAT and sales tax are worked out at checkout.
Questions
Does anything leave my machine?
Not through ADE: it has no network code, and its usage records and telemetry stay in your project. The engines are another matter. Claude Code and Codex send your prompts and the code they read to Anthropic and OpenAI under your own account, and each has its own telemetry you can turn off. Read Claude Code's data usage and Codex's settings, or our summary.
Which engines does it drive?
Claude Code and Codex, from one roster. Agent definitions are generated for each from the same source, and ADE starts the real claude and codex binaries on your PATH.
Can I try it without spending usage?
Yes. Set ADE_PROVIDER=fake and every loop runs end to end with a fake engine. ade rehearse does one full loop per config option on throwaway repositories.
Do I need Orca?
No. Orca is an optional display that also carries alerts to your phone. The CLI-only mode has every instrument.
Will it change my global settings?
No. The committed settings hold permissions only. Machine-specific hooks go in a gitignored local file, and ade uninstall removes everything init generated.
What does it need?
Claude Code or Codex, signed in with your own account, and git on macOS or Linux. Each download carries its own Python (and git, on Windows), so nothing else is installed. The TypeScript starter also needs Node 22.6 or newer. No tmux and no background services: long runs detach with ade session on every platform. Install guide.