What changed
On July 17, Vercel announced that Chat SDK's Slack adapter now supports Slack's newer native agent messaging experience, not just basic bot replies. In practice, that means Chat SDK apps can opt into Slack's agent-specific UI with an Agent badge, conversations in Slack's Messages tab, suggested prompts, rotating status messages, and built-in thumbs-up or thumbs-down feedback controls. Vercel's announcement also shows the feature as a small config change on the adapter, instead of a large amount of custom Slack integration work. Vercel announcement
Why it matters
This matters because Slack changed the direction of its agent product surface on June 30. Slack's official agent messaging experience moves conversations into the regular Messages tab, makes agent_view the path for new apps, and changes how prompts, thread handling, and initial user interaction work. That means teams building workplace agents now need to target Slack's native agent UX rather than treating Slack as a plain chat transport. Slack agent messaging experience Slack manifest reference
The product angle
The interesting shift is that Vercel is packaging Slack-native agent UX as framework behavior. The Chat SDK adapter now exposes agentView, prompt suggestions, loading messages, streaming fallbacks, and feedback buttons in one place, so the product work moves from "how do we simulate an agent inside Slack?" to "what should this agent actually do for the team?" That lowers the surface area for internal tools, support agents, and workflow copilots that need to feel native on day one. Chat SDK Slack adapter docs
Builder takeaway
If you already have a Slack bot or an internal AI assistant, this update shortens the path to a more native product experience. The practical win is not just better UI polish. It is that streaming, prompt starters, feedback capture, and Slack-specific agent context now arrive as defaults in the framework. One caveat from Vercel's docs is worth noting: under agent_view, Slack threads each user message individually, so builders should rely on Chat SDK transcripts for conversation history instead of assuming Slack DM history alone is enough. That is a useful reminder that agent UX and agent state are now separate product decisions.