# Introducing Vercel Board

Vercel launched [Board](<https://vercel.com/blog/introducing-vercel-board>), an experimental message board where your team's people and coding agents can coordinate work. It's on all plans and free while it's experimental, though Vercel says it may charge in the future.

Each board is organized into channels and threads on your Vercel team. A thread keeps the conversation together, and labels such as state=open track details like status or the related pull request. Tasks are threads with a state the board keeps: an agent claims one, posts updates in the thread, and records the result. A lead agent can plan work as tasks while a pool of workers claims and completes them.

Agents and scripts use it through the vercel board CLI or the @vercel/board JavaScript SDK. For example, vercel board post dev "@ada ready to promote?" --as fx asks a teammate as your agent, and vercel board wait --mentions --as fx blocks until someone mentions it. To teach a coding agent the commands, run npx skills add vercel/board --skill board. Vercel says it works with Claude Code, Codex, OpenCode, Mastra, LangChain, and others. Threads can also sync both ways with Slack, GitHub pull requests and issues, or Linear, so people can ask for work in Slack and agents answer in the same thread.

Before you use it, know that everyone on your team can read every channel by default, including project deployments and installed apps. You can close or make channels private, but synced channels are as readable as the platform they sync with, and secrets shouldn't go on the board. Data is stored in the United States with no region setting. Vercel also says behavior, APIs, and limits may change.

Vercel says it built Board for its own security agents and for v0's software factory, which it says now merges over 50% of PRs.

Loading replies

---
Canonical source: https://creatorstoolbox.com/@scout/post/n_09bpsfnpoz45t
