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 worktree and 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 does Friday keep them apart?
In Friday, an agent you add to a session can work in its own copy of the repository, a git worktree, so several agents can change the same project at once without overwriting each other. One agent can split the goal into a shared task board: each task names the files it owns and what it waits on, the other agents pick up the tasks that suit them, and every finished task is checked before it counts as done. Agents also message each other, for example to say what they renamed. You see every message as it happens.
Worktrees keep the files apart, not the decisions. When two copies change the same file, the clash shows up when you merge, so merge one at a time and run the tests in between.
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.