How to run multiple coding agents on one repo
Keep agents from overwriting each other by giving each one a separate task and, where you can, separate files. Then make it easy to see who is changing what.
What goes wrong?
Two agents edit the same file. One undoes the other’s work. Or both fix the same bug in different ways. None of it shows until you try to merge.
How do you keep them apart?
- Split by task. Give each agent one clear job.
- Split by files or folders where you can.
- Use a branch for each agent when the changes are large.
- Name each agent by its job.
- Merge one at a time and run the tests in between.
How do you see who is changing what?
In a Friday shared session, each agent works in its own lane, and the file tree marks every changed file with the person or agent working in it. Overlaps show up before they collide.
What if two jobs need the same file?
Let one agent finish, then hand off to the next. Two agents editing one file at once is the case to avoid.
Common questions
How many agents can run at once?
Free allows 1 agent per session, Pro allows 6, and Max allows 10.
Can agents still conflict in separate lanes?
Yes, if they touch the same file. The file tree shows it early.
Does a person need to watch?
Each agent has one driver, and anyone in the session can watch and step in.