Skip to main content
Update

Anthropic ships a cookbook wiring Claude Managed Agents into Vercel Chat SDK

Anthropic published a new quickstart showing how to wire Claude Managed Agents into Vercel Chat SDK, so one agent can talk on the web, Slack, Teams, and Discord through a single handler, with Managed Agents handling session and memory.

By Nattapon YongpaiboonCo-founder, Claude Thailand Community

ClaudeDevs, Anthropic’s official developer account, announced a new cookbook showing how to wire Claude Managed Agents into Vercel’s Chat SDK, aimed squarely at people building agents on the Claude API. The sample code lives in the anthropics/claude-quickstarts repo, under managed-agents/chat-sdk.

Illustration of two boxes joined by a single line. The left box is Vercel Chat SDK with icons for Slack, Teams, Discord, and the web, plus a label noting 30-plus more platforms. The connecting line is labeled with a single handler, onDirectMessage. The right box is Claude Managed Agents, showing a reply streaming word by word and a strip underneath showing an active web-search tool call

A clean split of responsibilities

Vercel’s Chat SDK owns the entire chat surface through a single handler, onDirectMessage, with official adapters for Slack, Microsoft Teams, Google Chat, Discord, Telegram, GitHub, Linear, and WhatsApp, plus several community-built adapters. Per Vercel’s own feature announcement, Chat SDK reaches 30-plus other platforms beyond that by swapping the adapter, not rewriting the bot.

Claude Managed Agents runs the agent server-side end to end, model, tools, and session state included. Every chat becomes one long-lived session, and that session is what actually stores the conversation, so you don’t need to run your own database to keep chat history.

Notable features

Per Vercel’s announcement page:

  • Token-by-token streaming so replies render like they’re being typed live, over a single response.
  • A live activity feed showing which tool the agent is calling mid-turn.
  • Moving the same agent to another platform (say, from Slack to Discord) is a matter of swapping the adapter in a few lines, not rebuilding the bot.

The cookbook’s example

The quickstart’s example is a research analyst agent you chat with in a browser window first, with a ready-made template for deploying the same agent to Slack. The web version needs only one credential, Anthropic’s, with no platform-specific webhook setup or verification.

For the tool-execution environment (like web search), Claude Managed Agents ships with a built-in one that needs no extra setup. If you want more control, Anthropic also lets you bring your own sandbox instead, such as Vercel Sandbox, per Managed Agents’ self-hosted sandboxes documentation, which has its own dedicated cookbook for wiring up Vercel Sandbox specifically, at anthropics/claude-cookbooks.

Writer’s take

What stands out most to me is the clean division of labor. Instead of writing glue code for every chat platform yourself, which is repetitive, time-consuming work once an agent goes into real use, Chat SDK takes that off your hands entirely, while Managed Agents removes the need to manage session and memory yourself. For anyone in the community building agents on the Claude API, this is a real shortcut to putting one agent in front of users across several channels much faster.


Details in this article come from ClaudeDevs’ announcement on X (Twitter), Vercel’s feature announcement and blog post, and the source code in anthropics/claude-quickstarts. Read the originals via the links below.

Read the original >

Get it by email

New articles, Claude updates and community event announcements. Sent occasionally, never often enough to annoy you.

The newsletter is written in Thai

Carry on the conversation in our Facebook group

Ask questions, share techniques, show your work and hear about upcoming events. The group is where most of the talking happens.