I think the first question is what exactly are we trying to preserve by using either worktrees or multiple clones? The answer is: non-pushed changes So if all

I think the first question is what exactly are we trying to preserve by using either worktrees or multiple clones? The answer is: non-pushed changes So if all you want is to work on index.ts in a separate dir from api.ts then worktrees might work well If you want to be able to rm -rf one of the dirs without wondering about dependencies then yeah multiple clones makes sense Either way is a way to avoid using more fragile/finicky workflows like stash and stash pop