Sandbox demo
Migration Squad
N agents, N worktrees, leaf-first batches. The repo stays green the whole way.
Migrations — JS → TS, library upgrades, framework bumps — are bookkeeping at scale, and bookkeeping parallelizes. The shape: plan the dependency order once, then fan the modules out across agents in separate git worktrees, one module per PR, tests green at every step. The worktrees are what make the parallelism safe; the leaf-first order is what keeps it green.
Sandbox transcript
Press Play to replay this transcript step-by-step.
0 / 9
The transcript is canned — no real API calls. The point is to internalize the loop: user → plan → tool → result → answer.
Check your understanding
Q1. Why migrate one module per PR rather than one big migration PR?
· Score 100% on the quiz.