A swarm rider is one person who steers many coding agents and decides what they work on. The agents write. The rider picks the goal, the checks, and when to stop. It is swarm coding with a name. It is not a hive.
The short line this site uses:
- Vibe coding is one human and one AI.
- Swarm coding is one human and many AIs. A swarm rider is that person.
- Hive coding is many people and many AIs. The definition is What is hive coding?.
The glossary line is swarm rider. Who decides in the product modes next door is Swarm vs multiplayer vs hive coding.
Where the name comes from
On November 10, 2026, Matt Huang published "Swarm Riders and Swarm-Native Companies". He describes a class of people who are "capable of consistently commanding large swarms of agents to productive ends," and he calls that a new kind of managerial skill, different from managing people and more technical. The essay says it was first posted on X the same day. The essay is about a skill and about companies organized around it. It is not a public suggestion queue.
On November 17, 2026, Agent Relay published a case study of one customer, Pomerado, written by Khaliq Gant (the case study). Gant calls the two founders swarm riders. He quotes co-founder Alan Ma: "We average around ~40 agents / subagents now, sometimes jumping up to 80+ across two machines."
That "80+" is Ma's number, about one company, in the vendor's own case study. It is not a count of swarm riders in general, and it is not a result this site measured. The same piece reports large speed gains in the founders' words. This page uses the case study for the name and for the scale they described. It does not treat those speed claims as settled.
What the rider does
One person holds the list of work. Agents take pieces of it, often at the same time, in separate chats, on a shared board, or through a tool that lets them message each other. The rider throws out the bad attempts and keeps a result.
Google's /swarm command is a product version of the same shape. One person starts it. Workers and a verifier share a board. The result comes back to that person. The docs were checked for this site on November 16, 2026, in What is swarm coding?. If the docs have moved since, trust Google's swarm page.
The skill Huang named is real work: point a lot of agents at something that is actually wanted, and stop them when it is not. The agents do not take requests from people the rider has not already decided to hear.
A rider and a hive
| Swarm rider | Hive | |
|---|---|---|
| Who decides what gets built | One person | An open community, by public suggestions and votes |
| Who writes | Many agents | A coding agent the maintainer connects |
| Who can ask for a change | The rider, and whoever that person already listens to | Anyone, in public |
| Who merges | The rider | A named person, who may also be a rider |
| What the record shows | The person who ran the agents | The person who asked, and the person who merged |
A swarm rider can be the maintainer of a hive. The swarm can be how an accepted suggestion gets written. The community is what makes it hive coding. Without the open queue, it is one person and many agents, however large the swarm.
A shared board, a mission, and a factory are ways to run the swarm. They are covered in Agent swarms just became a feature. The factory, as a system separate from the product decision, is in Software factory vs hive coding.
The honest worry
A large swarm makes two old problems louder.
The rider becomes the queue. The Agent Relay case study quotes Ma on the stretch when their free allowance of relay calls ran out. The agents had to use the founders as the go-between. Ma said they "ended up being a bottleneck." That is one customer, describing one interruption, in the vendor's write-up. It is still the shape of the job. When the agents cannot settle the work among themselves, the person is the line.
A click is not a review. One person cannot carefully read what dozens of agents produce. The failure mode has a name. On November 4, 2026, Thoughtworks published a Technology Radar blip, status Caution, for human-in-the-loop theater: a human left in the loop as an empty approval, signing actions, prompts, or diffs they cannot realistically evaluate. The blip, and a Harvard working paper that finds code review becoming the bottleneck after firms adopt AI coding agents, are both in Who verifies the verifier?. This page does not repeat their numbers.
Hive coding does not give one maintainer more hours. It changes who fills the list, and it keeps a rule that only works if you honor it. Other people suggest and vote in public, so the rider is not the only person inventing the work. A person still merges, which counts only when the change is small enough to judge. Community text reaches an agent as a quoted request a person already approved, not as a raw order. Those rules, and the ways they fail, are in Is hive coding safe?.
The Hive Code is live and just opened. It is not a swarm product, and it does not run the agents. On October 26, 2026 the Hive pulse showed 0 ideas posted today, 0 ships this week, and 1 hiver. There is no crowd here to point at yet.
Frequently asked questions
What is a swarm rider?
A person who steers many coding agents and decides what they work on. Matt Huang used the name in a public essay on November 10, 2026, for people who can consistently command large swarms of agents to productive ends. One person decides. A hive is many people.
Is a swarm rider the same as a hive?
No. A swarm rider is one human and many AIs. A hive is many people and many AIs: an open community decides what is worth building, agents build it, and a named person merges. A rider can be that person. The open queue is the difference.
Where did the 80 agents figure come from?
From one customer, in a case study Agent Relay published on November 17, 2026. The case study calls two founders swarm riders, and quotes Pomerado co-founder Alan Ma saying they average about 40 agents and sometimes go past 80, across two machines. That is his account, not an industry average.
What is the risk of one person steering a large swarm?
The person either becomes the bottleneck or approves work they cannot really judge. Thoughtworks calls the second failure human-in-the-loop theater. The practical worries for a community, and the rules that answer them, are in the safety guide.
Can a swarm rider take part in hive coding?
Yes. The rider can be the maintainer. The swarm can write the accepted suggestions. It is hive coding when people who are not the rider can suggest and vote in public, and a person still merges.
One rider is a real start
If the work is yours, a swarm is a fair way to move. If people who are not at your keyboard should be able to say what gets built, the next step is a public queue, and a person on the merge who can still read the change.
Sign up free and post the first idea
Keep reading: