Might be a dumb question but can you explain in a couple words the benefit VS a well organized claude code CLI that knows to spin sub agents?
I had the same question. I think this is in the space of being like the 'trillian' or 'matrix' of ai agents, using multi provider coding agent from a single interface plus some bells and whistles.
But I think within claude code and codex subagent support has improved a lot lately and it doesn't seem this would improve that much over that native support if you only use one provider.
The benefit is not spinning up sub-agents, but spinning up parallel workstreams. They basically took 90% of the friction out of working with and using worktrees. I was using Linear a lot (and enjoying it!) for my issue tracking, but at some point I realized it's more productive to just create a new worktree in Conductor for any bug/feature and cut out the middleman.
hmm so working on different features let's say on the same git, in parallel, without causing issues? Is the improvement of this parallelization worth it on solo projects or it becomes only relevant on big projects with lots of PRs and such?
It's always useful to have even if you don't need 8 worktrees with agents all going at the same time (I rarely have more than 2-3 active at a time). Typically there a tension between the 'fast way' (a big ol' slop branch bag of assorted changes) and the 'correct way' (carefully isolated branches and PRs) - with a smart implementation of worktrees like Conductor, the correct way becomes just as fast. That's basically the heart of good UX in my mind.