Chat SDK now includes AI SDK tools: agent features need permission design first
On May 20, 2026, Vercel announced that Chat SDK now includes an AI SDK toolset. The important pieces are the new chat/ai subpath and createChatTools(chat), which connect Chat SDK read and write actions to an agent with less glue code.
What changed
Teams previously had to define application-specific tools for reading chat state, sending messages, or moderating conversations. This update makes that path more official and more reusable.
Why it matters
The hard part of agent features is not only model calling. It is application authority. Read tools are usually lower risk. Write tools can send messages or change state. The fact that write tools are gated by approval by default is the right product signal.
What developers should check now
- Do not give read tools and write tools the same trust level.
- Separate actions that can run automatically from actions that need user approval.
- Log tool calls made by the agent.
- When migrating, check deprecated exports and move AI-facing helpers to
chat/ai.
Practical takeaway
This is another step from “chatbot” toward “chat agent that can act.” The quality bar will increasingly be permission design, approvals, logs, and rollback paths, not just model quality.