I just built a quick plugin to automatically add agents & skills then fire off a team with them, depending on your task: https://github.com/drbscl/dream-team

I personally have no use for this type of workflow. I like parallel claude code instances in worktrees but nothing beyond that

Been waiting for this to drop and excited to test it out. We've been building something in this space - https://github.com/AgentWorkforce/relay, a real-time messaging layer that lets AI coding agents talk to each other across any CLI.

Assign roles to different models and have them coordinate: Claude as the lead, Codex on backend, Gemini on frontend, etc.

I wrote about my experiences with multi-agent orchestration here: https://x.com/khaliqgant/status/2019124627860050109?s=46

Subagents are out, put it all on agent teams!

something i really like from tryin git out over the last 10 minutes is that the main agent will continue talking to you while other agents are working, so you don't have to queue a message

Clean up the team

A cynical read of this is that it’s all a ploy to maximize usage.

Why do agents need to speak to each other if they’re just doing the work correctly the first time?

Is it an admission that a single agent is not useful and reliable enough?

Claude Town

Excited to try this out. I've seen a lot of working systems on my own computer that share files to talk between different Claude Code agents and I think this could work similarly to that.

(i thought gas town was satire? people in comments here seem to be saying that gas town also had multi-agent file sharing for work tracking)

Gas Town decimated by Claude bomb from orbit