Running workers in parallel without collisions

Two researchers asking non-overlapping questions can run at once with no ceremony — reads don't collide. The moment anything writes, parallelism needs a plan.

Exclusive file ownership is the simplest version. Before fanning out work that edits, write down which agent owns which paths, with no path appearing twice and no ambiguity about who owns a shared file. Two agents editing the same file concurrently produces a result that belongs to neither and reflects whichever finished last.

Isolated working areas are the stronger version, and git already has the mechanism: a worktree is a second checkout of the same repository in its own directory, so two lines of work proceed without touching each other or your main tree. Claude Code can start a session directly in one with --worktree, which is how you run two experimental changes and keep the option of discarding either.

claude --worktree try-fetch
claude --worktree try-axios

# each session works in its own checkout;
# your main working tree stays untouched

Whichever you use, integration stays with one owner. Parallel workers propose; a single person or session decides what lands. Skip that and you get two half-integrated changes and no one who can describe the resulting state.

Loading your workspace…