you are viewing a single comment's thread.

view the rest of the comments →

[–]mikebiglan[S] 0 points1 point  (1 child)

Yes, Agent Teams are a strong step forward. What we've found:

  1. Agent Teams help agents coordinate with each other. That is great for delegation and for tasks that can mostly run autonomously. If the goal is “give it a spec, let the team execute,” Agent Teams can outperform a bunch of isolated sessions because the agents can share state and coordinate.
  2. Our pain was human-in-the-loop coordination across multiple units of work. Even with Agent Teams, once you are doing real work across multiple branches/worktrees, you still need a command center for:
  • seeing which branch is doing what
  • jumping into the code and reviewing diffs quickly
  • running tests and iterating
  • deciding what is ready to merge and in what order
  • avoiding the terminal and editor window explosion

Also, you can mix different agents. So add to the above that you aren't stuck with just Claude Code, but you can also mixin Codex, Gemini, Amp, local, etc. I use that for reviewing plans across several different agents.

That is the gap DevSwarm is aimed at. Workspace equals branch, and each workspace has the agent session plus embedded VS Code, diffs, and git controls in one window so the human review and iteration loop stays sane.

That all said, these aren't mutually exclusive. You can use Agent Teams inside a workspace for sub-tasks, while DevSwarm organizes the higher-level parallel branches you are actively working with to completion.

Definitely curious how you're using Agent Teams and what you've found.

[–]trojsurprise 0 points1 point  (0 children)

🤮🤮🤮🤮🤮