Show HN: DevSwarm 2.0, fix parallel Claude Code sprawl
5 comments
Very cool. I'll definitely give this a try. I'd say code review is the most important part of a tool like this for me. How does it compare to Conductor?
CTO Here!
Definitely lots of parallels with Conductor, here's where I think we differentiate specifically.
* The interface to interact with your AI is a full IDE (our minimal fork of vscode) with a focus on the CLI AI
* Further, each workspace gets their own IDE with all the functionality that implies
* We support a bunch of different CLI AI
* Since it's a vscode fork, you have access to the open source extension marketplace so you can even use the extension AI's like Roo Code in parallel (or your favorite CLI AI's extension like the Claude Code extension which you can see in our video!)
* I believe our take on running your app in parallel is a bit different (I may be wrong though!). We provide a means to name variables that will bind to ports so your parallel runs of your app don't fight over ports
* Github PR review right in DevSwarm, leave comments and approvals! We are definitely in the same space for sure, our aim with DevSwarm 2.0 was to make the transition to multi-task/parallel development less of a sheer cliff.
For many folks diving into AI First development multi-tasking with worktrees was really intuitive, but taking a step back it's a pretty huge ask to make that pivot. DevSwarm 2.0 we think really helps bridge that gap.
Definitely lots of parallels with Conductor, here's where I think we differentiate specifically.
* The interface to interact with your AI is a full IDE (our minimal fork of vscode) with a focus on the CLI AI
* Further, each workspace gets their own IDE with all the functionality that implies
* We support a bunch of different CLI AI
* Since it's a vscode fork, you have access to the open source extension marketplace so you can even use the extension AI's like Roo Code in parallel (or your favorite CLI AI's extension like the Claude Code extension which you can see in our video!)
* I believe our take on running your app in parallel is a bit different (I may be wrong though!). We provide a means to name variables that will bind to ports so your parallel runs of your app don't fight over ports
* Github PR review right in DevSwarm, leave comments and approvals! We are definitely in the same space for sure, our aim with DevSwarm 2.0 was to make the transition to multi-task/parallel development less of a sheer cliff.
For many folks diving into AI First development multi-tasking with worktrees was really intuitive, but taking a step back it's a pretty huge ask to make that pivot. DevSwarm 2.0 we think really helps bridge that gap.
Yes, think Conductor meets Warp meets VS Code, all in one.
Plus full PR-mode support within. Full Jira integration.
Plus full PR-mode support within. Full Jira integration.
I’ve been using Claude Code heavily for the last few months (multiple Max plans). Running sessions in parallel across git branches or worktrees is fast, but it breaks down quickly in practice because of sprawl. Terminals everywhere, editor windows everywhere, and you lose track of basics like which agent is on which branch and what is ready for review.
DevSwarm is what we built to solve that.
The core abstraction is simple: workspace equals branch. Each workspace runs its agent session(s) and keeps the state visible. In 2.0 we added a full VS Code IDE embedded in each workspace, so editing, terminals, diffs, and git controls stay in one window while you jump between parallel branches.
I’d love blunt feedback from people doing parallel workflows:
Video: https://www.youtube.com/watch?v=MqRkSRee6HE
Download: https://devswarm.ai/download