4 ms·
That works when you just do it once. Where you can run into problems is when you do that twice. One instance might change a file one way, and the other might ch
by simonbw 1y ago
That works when you just do it once. Where you can run into problems is when you do that twice. One instance might change a file one way, and the other might change it in a conflicting way, then you have two Claudes getting confused about the state of that file and it gets messy. You can solve this by checking out multiple copies of your repo and having only one instance of Claude working per copy. This app seems like it just provides you with a nice UI for doing that.
- deleted 1y ago[deleted]
- lmeyerov 1y agoYes that's how I do Claude code manually, git branch per terminal window, and very rarely multiple agents on the same branch It mostly works, except we don't have a clean flow for docker: shared system daemon & repository means need to manually tag & run by branch/project (docker compose -p ...), which is friction for the LLM and even more setup than we want As a heavy multi session Claude Code user, this may be what finally converts me to cloud IDEs...
- oulu2006 1y agoI just do it with multiple terminals + checkouts + branches -- this seems to just get in the way. But I'm an old school vim/emacs keyboard only hacker, so terminal all the way is super efficient for me