Vercel’s v0 software factory now merges more than 50% of its pull requests without a human touching them. The system behind that number shipped to everyone yesterday. It’s called Vercel Board, and it’s what happens when you build agent coordination from scratch instead of bending Slack into a task manager.
Infra, Not a Product
Board is not a UI. Guillermo Rauch was explicit about that in the announcement: “It’s infra not product. I love the ‘headless Slack’ for agents analogy, because UI is free now.” The pitch is that you generate the interface that fits each use case — a security dashboard looks different from a build pipeline dashboard — and Board handles the coordination layer underneath.
The data model is straightforward. A board contains channels. Channels are path-style identifiers like dev or www/production. Channels contain threads. A thread is a root message plus replies, with status labels and optional PR links. Agents and humans post to threads. Agents claim them, work on them, and mark them done. The whole record stays together.
What Standard Tools Were Missing
Message queues handle delivery. Slack handles conversation. Linear handles human sprints. None of them were built with agents as first-class actors. The gaps become obvious fast: who prevents two agents from picking up the same task? How does a downstream agent know when upstream work is done without polling? Where do humans see what agents are doing without opening 12 terminal windows?
Board adds the missing pieces: task claiming with leases (so only one agent holds a task at a time), watcher-based wake-ups (an agent sleeps until a reply arrives), scheduled follow-ups, structured data schemas per channel, and per-channel access grants. Audit logs track every action. It’s not magic — it’s the primitives that every agent swarm has been reinventing independently.
The v0 Proof
Vercel didn’t build Board for the launch announcement. They built it because they needed it. The first deployment was a swarm of security agents analyzing Vercel’s codebases for vulnerabilities and pushing fixes — with Board tracking what each agent found, claimed, and resolved. Then came v0’s software factory, rebuilt entirely on Board. The result: 50% of v0 PRs now merge without human intervention.
That’s not a benchmark. That’s production.
Agents and Integrations
Board isn’t Vercel-locked in terms of which agents can use it. The official list includes Claude Code, Codex, Pi, OpenCode, eve, fx, Mastra, LangChain, and the Vercel AI SDK. Any agent that can run a CLI command or call a JavaScript SDK can participate in a Board workflow.
Access is through the Vercel CLI or the Board JavaScript SDK. Two-way sync with Slack and GitHub is available through Vercel Connect — replies, reactions, and edits flow both directions. All Vercel plans can access Board today in experimental status.
# Post a task to a channel
vercel board post --channel dev
# Claim from an agent
vercel board claim thread-id
# Mark done
vercel board reply thread-id --status done
What to Know Before Using It
Two current limitations are worth flagging. First, access tokens are team-scoped, not channel-scoped — if you need different agents to have access only to specific channels in a large org, you’re working around this for now. Second, Board is Vercel infrastructure, so message content is visible to Vercel. If that’s a constraint, it’s the wrong tool.
The community analysis on The New Stack also points out that event streaming with cursors and atomic task claiming semantics are gaps that may matter for high-throughput swarms. These are early days.
The Bigger Picture
The multi-agent coordination problem has spawned a pile of partial solutions in 2026 — AutoSwarm, Replit Missions, Perplexity Multiagent. Most of them bundle the orchestration logic into the product. Board’s bet is different: ship the primitive, let teams build the factory. Rauch described it as “an important building block for software factories, self-optimizing systems, and scientific research, where the human prompting is just the seed of the system.”
Whether that’s right depends on whether developers actually want to assemble their own coordination layer or just want something that works. The v0 numbers suggest Board works. The experimental label suggests Vercel is still figuring out the full scope.
For now, it’s available on all Vercel plans. Try it, or read the software factory post first to see how Vercel deployed it internally.

