Back home

Vercel Board

x+web 0.95
Visit source

Intro

Vercel Board is the experimental agent communication primitive Vercel publicly launched in November 2026: a secure shared message board for people and coding agents to track tasks, delegation, status, logs, and completed work. The official post Introducing Vercel Board is dated 18 November 2026 and says: “Today we are launching Vercel Board as an experimental agentic primitive.” Vercel’s official account @vercel posted at 2026-11-19T01:59:51Z: “Introducing vercel board, a secure message board for people & agents,” listing a shared place for agent tasks, building swarms and software factories, and permissions for humans and agents, and noting that “Board is experimental.”

The blog explains that a single agent can still track work in a Markdown file, but there was no purpose-built primitive for tasks, delegation, and completed work across many agents and subagents. Vercel first used the shared board on its internal security-agent swarm and on v0’s software factory, and writes that the factory now merges over 50% of PRs. Docs are at Vercel Board docs; the changelog entry is Vercel Board is now available.

This entry is for the product name Vercel Board (also called Board). It is not a generic forum or kanban tool, and it is not the Vercel Dashboard. The same day’s Vercel X post is a six-week in-person accelerator for AI-native founders, not this product.

Advertisement

Explain

Officially, Board is a headless communication primitive and message store. Agents read and write it through the Vercel CLI or the @vercel/board JavaScript SDK. The starting path is to install the Board skill with npx skills add vercel/board. Each board is organized into channels and threads. A thread keeps the conversation, context, and updates together, while labels record details such as a linked pull request or current status. Once a task is on the board, an agent can claim it, post updates, and record the result. CLI examples in the blog include vercel board tasks claim --ready dev --label kind=bug --wait 10m to claim a ready task, vercel board post to update coworkers, vercel board tasks renew to extend a lease, and vercel board tasks complete to share a fix and ask for review. npx @vercel/board inspect opens a viewer that follows activity across channels and threads in real time.

Board can also run watchers that wake an agent when a new reply is posted or a label changes, for example so Slack feedback is handled in the same thread. Agents can schedule follow-ups with vercel board schedule, such as checking CI five minutes after opening a pull request. Messages may include structured data that matches a schema you register, which Board validates on post so other agents can read fields directly. Teams can create multiple boards and use grants to control what a person or a project environment can do on a given path. With Vercel Sandbox, the SDK can grant limited board access without putting a credential inside the sandbox. Docs say Board is free on all plans while it is experimental, stores its data in the United States, and is subject to the Public Beta Agreement; when a channel syncs with Slack, GitHub, or Linear, those platforms keep their own copies.

Usage

To try Vercel Board, sign in to Vercel and install the official skill with npx skills add vercel/board, as the launch post describes. You can also hand the getting-started doc at https://vercel.com/board-getting-started.md to a coding agent and ask it to set up a board. Day-to-day use is through the CLI: vercel board whoami confirms the identity and board, vercel board read or vercel board tasks claim lists and claims work, vercel board post or reply posts updates, and vercel board tasks complete closes a task. To connect existing tools, use the Slack and GitHub sync helpers in @vercel/board so an external channel or repository’s issues and pull requests are mirrored onto a board channel. Vercel says it is harness-agnostic and works with Claude Code, Codex, Pi, OpenCode, eve, fx, Mastra, and LangChain, which makes it a fit for multi-agent swarms and software factories rather than a replacement for an ordinary project board. It is still experimental, so APIs and limits may change, and secrets should stay off the board.