Vercel launches Chat SDK to ship agents across Slack, Discord, GitHub, and more from one codebase

What Vercel announced on X

On March 19, 2026, Vercel said the real bottleneck in its internal agent push was not model wiring but chat-platform plumbing. Every messaging product had different event models, threading rules, and streaming behavior, so teams that wanted agents in Slack, Discord, or GitHub kept rewriting integration logic. Vercel’s answer was Chat SDK, a new abstraction layer meant to remove that channel-specific overhead.

What the official launch post says

According to Vercel’s blog, Chat SDK is a TypeScript library for building bots that work across Slack, Microsoft Teams, Google Chat, Discord, Telegram, GitHub, and Linear from a single codebase. The core chat package handles routing and application logic, while adapters absorb platform-specific quirks. In practical terms, switching channels is supposed to mean swapping adapters rather than rewriting the bot.

The SDK automatically converts markdown into the format each platform expects, including during streamed responses.

It can include link preview content, referenced posts, and images directly in agent prompts to preserve conversational context.

Vercel added a production-ready PostgreSQL state adapter alongside existing Redis options.

The launch also expands support to WhatsApp, and Vercel says Chat SDK is open source and in public beta.

Why this matters

For many teams, agent adoption is less about building a model-powered assistant and more about getting that assistant into the places where people already work. If each chat surface requires different handling for mentions, tables, formatting, reactions, and streaming, the cost of distribution quickly outweighs the value of the agent itself. Vercel is trying to move that complexity into an adapter layer so developers can define behavior once and ship it across multiple collaboration surfaces.

That makes Chat SDK a meaningful piece of agent infrastructure rather than just another developer convenience library. It applies the same logic that made multi-model SDKs attractive: standardize the unstable integration layer so teams can spend more time on workflows and less time on transport quirks. If that approach works, the advantage will not just be faster bot development. It will be faster deployment into the channels where agent usage actually compounds, from chat apps to issue trackers and code review surfaces.

Sources: Vercel X post · Vercel Chat SDK launch post