Hello, I’m building a macOS image editor, check it out if you want at https://mojavepaint.app/ , it’s got a backlog of about 1000 features I’m working on. The flow for each is Spend 5 minutes writing out the description of what I want. I design as a I write, often deleting the first draft entirely and explaining a better design Claude Opus has gotten slower in the last few months, so I stare at the terminal for 5-10 minutes until Claude is done coding Build in XCode, test, maybe ask for revisions, then commit I’m trying to think of a good way to make this more parallel. I’d want to kick off multiple step 1’s, then do all the step 3’s serially as soon as any particular Claude session is done. But without having multiple instances of XCode running, and without losing my session context after the code is written and I continue iterating, and without branch merging. So basically, for each of [1 … n], have a tab in my terminal each with a Claude session, that can flip between working on a clean isolated copy of “main” while it’s churning, then working on main itself while I’m testing and validating. This way I don’t have to merge anything into to main. I especially don’t want untested changes that I haven’t run yet in main. As far as I can tell, git worktrees aren’t the answer here. submitted by /u/banana_zest
Originally posted by u/banana_zest on r/ClaudeCode
You must log in or # to comment.