I've played with git worktrees a few years back but until agents it was never that practical to have more than 2 worktrees at once. Now that it is practical, solving the poor usability makes sense for us.

▲

hmokiguess 8 hours ago | parent [-]

Appreciate your input but I don't understand what you mean here.

You had use cases before in which you wanted more than 2 worktrees at once in the past and needed to juggle between them at the speed of "practical"?

What were you doing back then (a few years back and before agents as you implied) that required this and that your solution now solves?

What poor usability are you referring to here? Is the rate of utilizing git-worktrees a metric you are measuring? That does not make sense to me.

I also watched the demo video, and I don't understand the value here. Perhaps I am not your target demographic, but I am trying to understand who is. Is this for vibe-coding side projects only? Would be nice if you had a more practical/real stakes example. The demo video did not land for me.

	▲	saddlepaddle 7 hours ago \| parent [-]
		Hmm I guess two good questions to check to see if this tool is useful for you is 1) do you use a cli coding agent for the vast majority of your work and 2) are you interested in using more than one at once? If those two assumptions are true, I think our UI is a nice way to make the git worktree workflow (a very common path to running multiple agents) a bit easier to manage! It handles copying over environment variables for you, setting up containers, and a lot of the other small things you need to think about when using git worktrees basically. Having a more practical video is a great call-out though, we should probably have a more deep dive video of an actual session!