Guides·Worktrees

git worktrees and parallel agents

git worktree is a fifteen-year-old command that became essential the moment agents could edit files on their own. One checkout per agent, one branch each, no stashing.

01

Start here

02

Every guide in this cluster

Git worktrees: the complete guide One repository, many working directories. The mechanics, the full command surface, and the six things that go wrong. 10 min How to run multiple Claude Code sessions in parallel Two to six agents at once: the isolation, the rate-limit math, and how to review the output without drowning. 10 min What is a git worktree, and why it suddenly matters The mental model, exactly what is shared and what is not, and why an eleven-year-old command became essential. 7 min git worktree add: every form of the command Every form of the command, every flag, and the seven errors you will meet, with the exact text of each. 7 min git worktree remove: cleaning up properly Removing cleanly, every refusal and what it means, and repairing the mess left by deleting a directory by hand. 7 min git worktree vs branch: they are not alternatives One is a pointer, the other is a directory. Why the comparison is a category error, and what the real choice is. 8 min git worktree cheat sheet: every command on one page All eight subcommands, every flag, real output for each, plus the recipes and shell functions worth keeping. 8 min git worktree prune: clearing stale worktree metadata What it clears, what it refuses to touch, the flags with real output, and how it differs from remove and repair. 8 min Worktrees and node_modules: the real cost, and how to avoid it Why every worktree needs its own install, what that actually costs, the three fixes that work, and the one that fails silently. 9 min Claude Code with git worktrees: the practical setup The built-in --worktree flag, what it creates, how Claude Code enforces the isolation, and when to reach for git instead. 10 min Running several Codex sessions at once A worktree per session, why the sandbox makes that isolation real, the approval settings that survive four sessions, and the three ceilings. 8 min git worktrees in VS Code: windows, workspaces, and search The built-in Source Control commands, the settings that matter, one window each versus multi-root, and the search and watcher traps. 8 min Claude Code orchestration: running a fleet without losing control The operating model for a Claude Code fleet: isolated branches, bounded tasks, visible state, fresh review, and a merge queue one person can actually control. 14 min Multi-agent development: run a team of agents, keep the repo The operating system for parallel coding agents: one task, branch, worktree, owner, proof bundle, and review slot at a time. 14 min Switch from Augment Code to Continuum safely A capability-by-capability migration for teams moving from Augment’s integrated context platform to a multi-agent workbench. 9 min Switch from Qodo to Continuum without losing code review This is usually a workflow expansion, not a direct replacement. Continuum coordinates coding agents; Qodo reviews and governs the changes they produce. 10 min
03

Other clusters

Try it

Every agent.
One workbench.

Continuum runs Claude Code, Codex, Cursor, Gemini, and more under the subscriptions you already pay for, with live quota gauges and spend by repo.

free app · your subscriptions · local-first