Give each Claude Code session one task, its own files and its own git worktree, and check their work together on a schedule. Never let two sessions edit the same file. You get several pieces of work moving at once without them stepping on each other. We set this up with teams so their work keeps moving while they review.
One task per session
Write each task in a few lines: what to change, which files, and what "done" looks like. Vague tasks drift.
Separate files, separate worktrees
Give each session its own git worktree, so its changes sit on their own branch. Split tasks so no two touch the same file.
A shared notes folder
Have sessions leave hand-over notes in one folder: what they changed, what's open, what they need. You read one place instead of every transcript.
Check together, on a schedule
Every so often, bring the finished branches together and check them as one. Problems show up where pieces meet.
You're the limit
Start only as many as you can review. Unreviewed work piles up and gets merged without anyone looking.
What goes wrong
| What you see | Why | Fix |
|---|---|---|
| Sessions overwrite each other | Same files, same folder | Own files, own worktree |
| Work drifts off course | Task too vague | Write what done looks like |
| You can't tell what happened | Everything is in transcripts | A shared notes folder |
| Pieces don't fit together | Never checked as one | Merge and check on a schedule |
Set it up with us
We'll set up how your team runs several sessions at once, from task splits to review, so more ships without more mess.
Questions
Can two Claude Code sessions work on the same repo?
Yes, if each has its own git worktree and its own files. Two sessions editing the same file will overwrite each other.
How many Claude Code sessions should I run at once?
As many as you can review. The limit is how fast you can check their work, not how many you can start.
How do I keep track of what each session is doing?
Give each one a short written task and a shared notes folder for hand-overs. Check them together on a schedule.
Originally published at wednesday.is.



