Claude Code's new hidden feature: Swarms

Claude Code in the desktop app seems to do this? It's crazy to watch. It sets of these huge swarms of worker readers under master task headings, that go off and explore the code base and compile huge reports and todo lists, then another system behind the scenes seems to be compiling everything to large master schemas/plans. I create helper files and then have a devops chat, a front end chat, an architecture chat and a security chat, and once each it done it's work it automatically writes to a log and the others pick up the log (it seems to have a system reminder process build in that can push updates from other chats into other chats. It's really wild to watch it work, and it's very intuitive and fun to use. I've not tried CLI claude code only claude code in the desktop app, but desktop app sftp to a droplet with ssh for it to use the terminal is a very very interesting experience, it can seem to just go for hours building, fixing, checking it's own work, loading it's work in the browser, doing more work etc all on it's own - it's how I built this: https://news.ycombinator.com/item?id=46724896 in 3 days.

This is just sub agents, built into Claude. You don’t need 300,000 line tmux abstractions written in go. You just tell Claude to do work in parallel with background sub agents. It helps to have a file for handing off the prompt, tracking progress, and reporting back. I also recommend constraining agents to their own worktrees. I am writing down the pattern here https://workforest.space while nearly everyone is building orchestrators i also noticed claude is already the best orchestrator for claude.

Looks like agent orchestrators provided by the foundation model providers will become a big theme in 2026. By wrapping it in terms that are already used in software development today like team leads, team members, etc. rather than inventing a completely new taxonomy of Polecats and Badgers, will help make it more successful and understandable.

Everyone is wrapping Claude Code in Tmux and claiming they are a magician. I am not so good at marketing but I've done this here https://github.com/mohsen1/claude-code-orchestrator

Mine also rotate between Claude or Z.ai accounts as they ran out of credits

How is this different from GSD: https://github.com/glittercowboy/get-shit-done

I've been using that and it's excellent

A guy who worked at docker on docker swarm now works at Anthropic so makes sense

Listen team lead and the whole team, make this button red.

I'm a fan of AI coding tools but the trend of adding ever more autonomy to agents confuses me.

The rate at which a person running these tools can review and comprehend the output properly is basically reached with just a single thread with a human in the loop.

Which implies that this is not intended to be used in a setting where people will be reading the code.

Does that... Actually work for anyone? My experience so far with AI tools would have me believe that it's a terrible idea.

It feels like Auto-GPT, BabyAGI, and the like were simply ahead of their time

Isn't this pretty much what Ruv has been building for like two years?

https://github.com/ruvnet/claude-flow

I'm already burning through enough tokens and producing more code than can be maintained - with just one claude worker. Feel like I need to move into the other direction, more personal hands-on "management".

And… how?

[dead]

Answering the question how to sell more tokens per customer while maintaining ~~mediocre~~ breakthrough results.