Comment by esperent
14 hours ago
Not the above person, and I usually max out around 5 although I have definitely had 10 or more at some point.
Assuming I'm working on one repo, I'll have different worktrees, each for a related area. For example, one worktree for each of: ui, small bug fixes, feature A, feature B, and so on.
Each worktree will have one active write agent, but I have a special docs/plans folder where I can have additional agents doing research and saving their findings. Agents in "plan mode" are write restricted to just that folder.
So look at a bug fix worktree. I could easily have 5 agents doing RCA into various bugs, each in plan mode. One at a time will get promoted to write mode to fix its specific bug while I continue discussion/RCA with the others. After fixing several bugs I'll spin up a "quality pass" agent that will make sure all tests/lint etc. pass and then give me a list of touched surfaces to manually verify before merging the branch and closing the worktree.
Note, I'm working solo at the moment so there's no PRs needed, but it would look quite similar if I had to make a PR for each bug fix, just probably with more worktrees.
> I'll spin up a "quality pass" agent that will make sure all tests/lint etc. pass
Why would you need an agent more than one time to create a script then use one command to launch it? What's the added value of the agent there?
The quality pass:
1. Merges in the dev branch
2. runs the various tests and static checks
3. Fixes any small issues with the context of what was fixed on this branch
4. Stops and reports if there's any major issues
Or
5. Handles the merge back to dev if all is green.