Vercel has released Board, an experimental service that lets agents from different vendors pull tasks off one shared queue, report back, and leave a record humans can audit. The company says it built the tool because its own agent fleets had outgrown the Markdown files a single agent uses to remember what it is doing, according to Vercel’s engineering blog.

The pitch is coordination infrastructure for the stage after one agent finishes one job. Vercel says two internal projects forced the issue: a group of security agents that scan its codebases for vulnerabilities and push fixes, and the pipeline behind v0, its app-building product. Vercel reports that the v0 pipeline, rebuilt on Board, now merges more than half of its pull requests. That figure is the company’s own, and the post offers no baseline for comparison.

Work on a board sits in channels, and each conversation lives in its own thread. That thread holds the original report, the discussion, and the resulting pull request, while labels carry status. An agent claims a task through a command-line tool or a JavaScript SDK, renews its lease if the job runs long, and marks it complete with a link for review. Vercel lists Claude Code, Codex, OpenCode, Mastra, and LangChain among the harnesses that can share a board.

Two features separate it from a plain chat log. First, watchers can wake an agent when a reply lands or a label changes, and on Vercel’s platform that wakes a deployment, so nothing has to run idle between events. Agents can also schedule their own follow-ups, such as checking CI five minutes after opening a pull request. Second, messages can carry structured data validated against a schema you register, so a security finding arrives as fields (repository, severity, status) instead of prose an agent must parse.

Access control gets equal billing. Boards take per-user and per-agent grants, every event records who acted, and a sandboxed agent can be given a board connection with no credential stored inside the sandbox, limited to named channels and actions. Two-way sync mirrors replies, edits, reactions, and deletions between Board and tools such as Slack and GitHub, so a bug reported in Slack can become an agent task and come back as a pull request in the same conversation.

The useful comparison is to the tracker your engineers already use. Linear and GitHub Issues assume a human is assigning and reading. Board assumes the worker is a process that claims, leases, and times out, and that dependencies between tasks decide what may run in parallel. Vercel describes a review task that becomes claimable only once its fix is complete, while unrelated fixes proceed at the same time.

The limits are plain. Vercel calls Board experimental, and it has published no pricing, scale figures, or failure-mode data, such as what happens when two agents hold conflicting leases. The only adoption evidence comes from Vercel’s own teams, who built the product for themselves. Anything keyed to a Vercel deployment also ties the wake-on-event feature to its hosting.

Even so, the design choices matter more than the product. Leases, schemas, and scoped grants are what teams will end up needing once agents outnumber the people supervising them, whoever supplies them. A team running more than a handful of agents today should test whether its current tracker can express a claim, a timeout, and a dependency, and if it cannot, Board’s CLI is a cheap way to find out where the gap sits.

Vercel, “Introducing Vercel Board,” vercel.com blog, accessed November 20, 2026 (the post carries no visible publication date).