Harness – Manage parallel Claude Code agents across Git worktrees
Runs ten Claude agents in parallel with global hooks tracking status across worktrees.

Workspace = branch for parallel Claude Code, but Cursor and Continue already multi-task agents.
Developers running parallel AI-assisted coding sessions across multiple git branches
Cursor · VS Code Remote Containers
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=MqRkSRee6HEDownload: https://devswarm.ai/download
Runs ten Claude agents in parallel with global hooks tracking status across worktrees.
4-pane terminals + cost tracking for Claude Code; Cursor workspaces already do this natively.
Built-in browser bridge lets agents click DOM elements directly from the terminal pane.
If you use Claude Code this is the kind of ergonomic tooling you didn’t know you wanted: it auto-discovers every session, groups them into workspaces, and surfaces 4-pane embedded terminals alongside per-workspace docs, kanban, templates and a costs dashboard. It’s local-first and runs via npx, which keeps your data in your browser, but the scope is narrowly tied to Claude and real terminal emulation requires native build tools (node-pty).
Parallel AI agent workspaces via git worktrees—solves a real coordination problem at scale.
Auto-titles from Haiku in ~10ms so parallel Claude sessions stay visually distinct.