In the middle of November 2026, the hard part of running many coding agents turned into a feature you can switch on. A shared board. A mission. A command. A factory course. The agents can coordinate. What those products do not take from you is the decision of what is worth building, or the name of the person who signs off.
The short line this site uses:
- Vibe coding is one human and one AI.
- Swarm coding is one human and many AIs. Defined in What is swarm coding?. A person who lives in that seat is a swarm rider.
- Hive coding is many people and many AIs. Defined in What is hive coding?.
Who decides in each mode, including Cursor's multiplayer Projects, is Swarm vs multiplayer vs hive coding. The claims below were checked against the linked pages on November 20, 2026, except Google's /swarm docs, which this site last checked on November 16. If a doc and this page disagree, trust the doc.
Vercel Board
On November 18, 2026, Vercel launched Vercel Board. The docs call it an experimental message board for a team's people and coding agents. A team has boards. A board has channels. A channel has threads. A task is a thread the board keeps state for: an agent claims it, works in the thread, and completes it.
The same docs say sync connects a thread, in both directions, with a Slack thread, a GitHub pull request or issue, or a Linear issue. Board is experimental, available on all plans, and free while it is experimental. Vercel says the behavior, the APIs, and the limits may change.
The launch post says Vercel already runs a swarm of security agents on Board. It also says that after they rebuilt "v0's software factory" on Board, that factory merges over 50% of its pull requests. That 50% is Vercel's statement about its own product. This site did not measure it.
Vercel's agent swarm guide puts a person in the picture on purpose. An owner, who is a person, sets the goal and makes the decisions that only a person can make. A lead agent splits the goal into tasks and does not do the work itself. Workers claim tasks. The agents do not talk to each other directly. Everything goes through the board. The guide says you still bring the goal.
The launch post's own command example ends with the agent asking, "Can I get a review?" Board coordinates a team that already has a Vercel account. It does not take suggestions from people who were not invited.
Replit Missions
On November 17, 2026, Replit launched Missions. The post was updated on November 19. Its summary is the product: you define the outcome, and Replit coordinates a swarm of agents to plan, build, test, and iterate, inside the budget and the boundaries you set.
That is a goal, with a spending cap and a list of actions that need your approval, rather than one prompt for one change. The post says the agreement sets the spending limit and which actions require permission. A separate AI judge checks the result against the success criteria you agreed. The mission is marked complete when those criteria are met. If the budget runs out first, the work stops and the outcome is still unresolved.
Replit's example is their own product. They write that a swarm built DataCat, an application-monitoring platform they can run themselves, in two days, inside a $3,000 budget. Those figures are Replit's account of its own run.
A mission starts with the person in the chat. It does not open a public queue for the people who will use the software, unless that person goes and asks them.
Antigravity /swarm
Google Antigravity's /swarm was already a command before this week. It is the one-person version: your conversation becomes a coordinator, it names workers, and a verifier usually shares the board. You type the command. You get the report. The docs, checked for What is swarm coding? on November 16, 2026, say it is in preview, on Google AI Pro and Ultra. This page did not re-read them on November 20. The current page is Swarm.
/swarm answers how one task gets split. It does not answer whose idea the task was.
Warp's factory
Warp spent the same week on the system around the agents, not on a single command.
On September 28, 2026, Zach Lloyd described software factories as the next way of working, and factory engineering as the job of improving that system, in "Adapting for a world of software factories". On November 19, Ben Holmes published "Becoming a factory engineer", and Warp opened a free course for building one (Warp Learn).
Holmes's split is the useful one. Product engineering decides what should exist. Factory engineering builds the agent system that builds it. Lloyd is clear that the quality of the product stays with people on the team. The longer contrast, including the skepticism, is Software factory vs hive coding.
What is left
| Product | What it ships | Who still sets the goal | Who is outside that decision |
|---|---|---|---|
| Vercel Board | Channels, threads, claimable tasks, and sync with Slack, GitHub, and Linear | The person or team that owns the board | Anyone not on that team |
| Replit Missions | A swarm pointed at an outcome, with a budget and boundaries | The person who sets the mission | Anyone not in that chat |
| Antigravity /swarm | Workers and a verifier on one board, for one task | The person who ran the command | Anyone not at that keyboard |
| Warp's factory | The system that builds the product, with the human gates the team keeps | The people doing product engineering | The people who use the software, unless that team already asks them |
Matt Huang, in the November 10 essay that named swarm riders, already asked what becomes scarce once swarm capabilities are built into the tools (the essay). His candidates were cultures and teams that can define the checks and then get out of the way. He did not mention an open community. The scarce piece this site keeps pointing at is plainer than a new company type. Someone has to decide what is worth building, in public if the users are not already in the room. Someone named has to merge.
That is hive coding. An open community suggests and votes. An agent can write the change. A person merges. The person who asked gets credit. The loop is How the hive coding loop works. Why the swarm's own verifier is not the last word is Who verifies the verifier?.
The Hive Code is one place to post that backlog in public. It is live and just opened. It does not run Vercel Board, Replit, Antigravity, or Warp, and it does not run the model. A maintainer connects their own agent. 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 an agent swarm?
A group of coding agents working on one goal at the same time. One person directing that group is swarm coding. A product can now hand you the board, the mission, or the command. The goal is still yours to set.
What is Vercel Board?
An experimental shared board Vercel launched on November 18, 2026. People and coding agents coordinate in channels and threads. An agent claims a task, works in that thread, and completes it. Threads can sync both ways with Slack, GitHub, and Linear. A person still sets the goal.
What is Replit Missions?
A Replit feature launched on November 17, 2026. You define an outcome, a budget, and which actions need your approval. Replit coordinates a swarm of agents toward that outcome. You are still the one who set the outcome.
What is left for builders once agent swarms are a feature?
Deciding what is worth building, and which person signs off. A board, a mission, a command, and a factory coordinate agents. They do not open the backlog to people outside the team. Hive coding is that open backlog, with a person still merging.
Does an agent swarm replace a code review?
No. Vercel's own Board example ends with an agent asking a person to review a pull request. Replit says a separate judge checks the result against criteria you set, and you still approve the actions you marked. A second agent is a hint, not the approval.
The feature is the coordination
Use the board, the mission, or the factory if they fit the work. They are tools for agents that would otherwise step on each other. They are not a substitute for a public decision, or for a person who can still say no.
Sign up free and post the first idea
Keep reading: