
Why it mattersA team running more than one agent needs one place for them to talk and record what they did. Vercel now offers that place as a product.
Six coding agents working on the same project each keep their own notes. None can see the others. Vercel posted a blog on 18 November that tries to fix this. The new product is called Board. Vercel describes it as "a headless communication primitive and message store for your agents across tools and environments". It is available on every plan, and marked experimental.
Board is a shared message store. Agents and humans post in channels and threads. A thread holds the discussion and the results of one task together. Labels mark things like the pull request an agent is working on, and the task's state. Permissions decide which channels an agent can read and write, and which actions it can take. Every action is recorded.
What it works with today
Vercel says Board works with Claude Code, Codex, Pi, OpenCode, eve, fx, Mastra, and LangChain. Agents reach Board through the Vercel CLI, through a JavaScript SDK, or by installing a skill with npx skills add vercel/board. Messages sync both ways with Slack and GitHub through Vercel Connect, and replies, reactions and edits sync in both directions. Vercel calls it an "experimental agentic primitive".
A number from inside Vercel
Vercel says v0's software factory runs on Board. It "now merges over 50% of PRs" without a human writing or reviewing them. The number is Vercel's own, for one Vercel product. No independent audit is attached. The post gives no earlier figure for the same factory. A reader cannot see the move from before to after.
Two features worth naming
Two parts of Board are built for the agent to read and write directly. The first is a schema on messages. A message carries structured fields an agent reads directly. The agent does not have to parse a sentence to find the pull request number or the task state. The second is a scheduler. An agent can claim a task and renew its claim, so two agents do not do the same work. Another agent can watch a channel and be woken when a message appears, so it does not have to poll.
The post is signed by Julian Benegas, Nicolás Montone, Malte Ubl, Tom Knickman, Martin Sione, and Bani Singh.
A team running one agent does not need Board. A team running several agents, each writing to its own Markdown file, now has one place to park the work. There is also a record of who did what. Reveneau's own agents write to one shared log. A human reviewer can replay a run end to end. The eval suite is written against the specification. It keeps working whether the agents coordinate in a file, in a Slack channel, or in Board.
Source
Introducing Vercel Board, Vercel. Vercel Board is now available, Vercel changelog.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
