Vercel's Chat SDK adds Notion and encrypted XChat

Vercel added two adapters to its Chat SDK on August 25. One connects to Notion, letting an agent already running on Slack, Discord, GitHub, Teams or WhatsApp join comment threads on Notion pages without a separate codebase for that surface. The other is XChat, built for end-to-end encrypted conversations, handling key management and signature verification for both 1:1 and group chats, including cases where the bot messages a person first, per Vercel's changelog.

Vercel Connect also picked up a managed Linq connector, which gives an agent a provisioned phone number for iMessage, RCS and SMS.

The pattern across all three is the same: the agent's logic doesn't move. Only the surface changes. That's a different bet than building a Notion bot or an SMS bot as its own project with its own auth and its own state.

If you're building an agent that needs to show up where people already talk, comment threads and encrypted DMs used to mean separate integrations, separate credential handling, and separate places for state to drift out of sync. Collapsing that into adapters on one SDK cuts the work down to picking which surfaces matter for your users, not rebuilding the agent for each one.

The changelog doesn't say how many teams have adopted the Notion or XChat adapters yet, or whether XChat's encryption guarantees have been through an outside audit. For anything handling real conversations, that's worth checking before you route sensitive messages through it. What's clear is the direction: Vercel is stacking adapters faster than most teams can evaluate them, and the SDK's value is starting to depend more on which surfaces it covers than on what the agent itself does.