Vercel launched Vercel Board on November 18 as an experimental, headless message store and coordination primitive for humans and agents. Agents read and write channels and threads through the CLI or the JavaScript SDK: they can claim tasks, renew leases, post updates and record results, while watchers wake agents on new replies and vercel board schedule sets follow-ups. Board adds two-way sync with Slack and GitHub, schema-validated structured messages and per-channel grants. Vercel says v0's software factory now runs on Board and merges over 50% of PRs.

Key Takeaways

  • ✓Positioning: an experimental, harness-agnostic coordination primitive that organizes tasks, context and results in channels and threads
  • ✓Compatibility: Claude Code, Codex, Pi, OpenCode, eve, fx, Mastra and LangChain can collaborate on the same board
  • ✓Features: task claiming with leases, task dependencies, watchers that wake agents on new replies, scheduled follow-ups, and two-way Slack and GitHub sync
  • ✓Access control: per-channel grants by user, project and environment, with every event recording who performed the action
  • ✓Internal use: Vercel security agent swarms and the v0 software factory, which now merges over 50% of PRs; get started with npx skills add vercel/board
Vercel Launches Experimental Vercel Board, a Shared Message Board Where Humans and Agents Claim Tasks, Schedule Follow-Ups and Sync Two-Way With Slack and GitHub
🖼️Official Media
Click to view high-res
⚡

Key Decision Metrics at a Glance

TL;DR Verdict
🧭

Turn your technical choice into a development budget

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

🔬

In-Depth Technical Analysis

Background

Development is moving from single agents doing tasks to teams of agents working on projects. One agent can track its work in a Markdown file, but there has been no purpose-built tool for tracking delegation, status, logs and output across many agents and subagents.

How it works

Board is a headless message store organized into channels and threads. Agents use the CLI or SDK to claim tasks (with renewable leases), post updates and record results, and tasks can depend on each other. Watchers wake agents when a new reply arrives or a label changes, and on Vercel no process has to stay running between events; vercel board schedule lets an agent come back in a few minutes to check CI. Messages can carry schema-validated structured data, and access can be granted per channel.

Benchmarks

Vercel published no benchmarks. The only figure is internal: after moving to Board, v0's software factory now merges over 50% of PRs.

What it means for developers

Run npx skills add vercel/board to give your agent instructions for using it, and npx @vercel/board inspect to watch activity across channels in real time. It is experimental, so try it first on internal work such as security scans or bug triage rather than critical workflows.

Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.

Up NextVercel ships Workflow SDK 5: durable engine rewritten for agent loops, up to 25x lower overhead, end-to-end encrypted payloads by default and per-region runs
Read Now→