Show HN: DevSwarm 2.0, fix parallel Claude Code sprawl

7 points by mikebiglan ↗ HN
Mike, cofounder of DevSwarm here.

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:

  • What breaks first for you past 2 parallel sessions?

  • What would you need for this to be production-grade? Tests, debugging, extensions, PR flow?
Video: https://www.youtube.com/watch?v=MqRkSRee6HE

Download: https://devswarm.ai/download

2 comments

[ 2.9 ms ] story [ 9.4 ms ] thread
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?
Looks slick. Linux version please!