The DropJuly 8, 2026via Vercel Blog
Use any Chat SDK adapter with eve
Why it matters
Vercel's new Chat SDK channel reduces friction for AI agent deployment across multiple platforms. This is a significant productivity multiplier for teams building multi-channel conversational AI products, lowering the engineering cost of distribution.
Key signals
- eve now supports Chat SDK adapters natively
- Single integration connects to Facebook Messenger, WhatsApp, Resend, Liveblocks, and other surfaces
- Webhook route auto-mounts for each adapter (e.g., /eve/v1/chat/slack)
- Built-in features: typing indicators, human-in-the-loop cards, thread persistence, proactive sends, failure reporting
- Handlers written once, work across all connected channels
- Published July 8, 2026
- New .eveChat SDK channel supports Facebook Messenger, WhatsApp, Resend, Liveblocks, and any Chat SDK adapter
- Single handler code routes to multiple surfaces via webhook mounts (e.g., /eve/v1/chat/slack)
- Built-in features: typing indicators, human-in-the-loop card UI, thread persistence, proactive sends, failure reporting
- Developers write standard Chat SDK handler code; calling send() inside a handler passes message to agent
- Published July 8, 2026 on Vercel changelog
The hook
Vercel just eliminated the integration tax. One eve agent now connects to Facebook Messenger, WhatsApp, Slack, and 20+ surfaces—no custom code per channel.
now supports Chat SDK adapters with the new .eveChat SDK channel
One channel connects your eve agent to Facebook Messenger, WhatsApp, Resend, Liveblocks, and any other surface with an . You write normal Chat SDK handler code, and calling inside a handler hands the message to your agent.adaptersend
Register handlers on exactly as you would in a standalone Chat SDK app.bot
Out of the box, the channel:
Supply your own handlers to override any of these defaults.events
Read the documentation to get started, or learn how to build your own .Chat SDK channeleve agent with Resend
Mounts a webhook route for each adapter (e.g., )/eve/v1/chat/slack
Shows a typing indicator while a turn runs, then posts the agent's reply
Renders human-in-the-loop input requests as cards with buttons, and resumes the session when one is clicked
Persists the thread, so later events, including proactive sends from schedules, reach the same conversation
Reports failures in the thread with a readable message