Vercel has opened an experimental service called Board that acts as a headless Slack‑style message board for AI agents. The platform lets agents written in different runtimes (Claude Code, Codex, Pi, OpenCode, eve, fx, Mastra, LangChain) pick up work items, post updates, and coordinate through threaded discussions that are persisted and visible to developers. Board also integrates with Slack, GitHub, and Linear, allowing a developer‑initiated request to be broken into sub‑tasks that agents can claim and execute.
Why the change matters to AI, cloud, and security engineers
Multi‑agent systems have shown scalability benefits—OpenAI reported 10,000 agents exchanging 2.7 million messages to solve the Navier‑Stokes problem. Vercel’s Board provides a concrete infrastructure layer for that pattern, moving the coordination problem from ad‑hoc scripts to a managed primitive. For engineers, this means a reusable way to orchestrate agents without building custom messaging or state‑sharing services.
Architectural considerations
Board sits between agents and existing developer tools. Its core responsibilities are:
- Channel and thread creation for task assignment.
- Persistent activity logs that can be queried by humans or other agents.
- Event‑driven triggers that wake agents when messages arrive or task status changes.
- Bidirectional sync with GitHub pull‑request objects and Linear tickets.
Because Board is model‑agnostic, it can be added to any existing CI/CD pipeline by installing Vercel’s CLI and pointing agents at the board endpoint. The service does not replace version control or issue tracking; it augments them with a lightweight coordination layer.
Implementation and operational impact
Vercel reports that after rebuilding its software factory around Board, more than half of its pull requests are merged automatically. The practical effect is a reduction in manual hand‑off between agents and developers. Teams can configure agents to:
- Listen for a Slack command (e.g., a security scan request).
- Create a Board thread, claim the top‑level task, and spawn subtasks for specialized agents.
- Post findings back to the thread, where a human can approve or reject the change.
- Trigger a GitHub PR update that is itself recorded as a Board message.
Operationally, this introduces a single point of coordination that must be monitored for availability and latency. The board’s history provides an audit trail, but teams need to ensure that the CLI and board endpoint are included in their observability stack.
Security and governance implications
Allowing agents to exchange information autonomously raises questions about control and data leakage. Board enforces channel‑level permissions, letting administrators decide which agents and human users can read or write in a given thread. Agents can be programmed to pause for human approval before committing code, preserving a manual checkpoint. However, the open‑ended nature of message exchange means that any compromised agent could potentially exfiltrate data or issue unauthorized commands unless the permission model is tightly scoped.
The recent OpenAI/Hugging Face incident, referenced by Vercel, illustrates how a shared message board can become a conduit for coordinated misuse. Practitioners should therefore treat Board as a privileged communication channel and apply the same scrutiny they would to any internal API.
Related CloudNinjas coverage: AI engineering.
What This Means For Practitioners
Board offers a pragmatic way to orchestrate heterogeneous AI agents while keeping developers in the loop. Evaluate it as a coordination layer if you already run multiple coding or security agents and need a persistent, auditable task flow. Start by mapping existing Slack or GitHub workflows to Board threads, enforce strict channel permissions, and instrument the board’s CLI for health checks. Monitor the board’s activity logs for unexpected patterns, and treat the board as a critical component in your security threat model.



