Not sure if others are approaching this differently, but I’m regularly using three or four tabs to handle work on different features that aren’t truly “connected” in my app (so safe to work concurrently), in the sense that they don’t share areas or categories in my app, but they may have some overlap at the database level. What I’m seeing is that, by using multiple tabs, when it comes time to commit and ultimately push the code, the agent recognizes other work being done and spends almost as much time determining what goes into the commit from this tab and working to limit it as it did to develop the entire iteration of the feature. Seems like whatever gain is realized from concurrent work is lost or severely limited by each agents “surprise” realization that there is other work going on. Any tips here?
Hey there!
Worktrees are a common approach to this problem. While they may not be the definitive solution for resolving conflicts between multiple agents working in parallel, they currently offer a solid way to isolate changes.