Channels SDK: Your Agent Moves into Slack
CopilotKit open-sourced the Channels SDK, an MIT-licensed library that puts any agent inside Slack and Microsoft Teams with native interactive UI (github.com/CopilotKit/channels-sdk). The Show HN made the front page on August 6. Slack and Teams are generally available now; Discord, Telegram and WhatsApp adapters are in the package with more coming.
The key design choice is that it builds on AG-UI, CopilotKit's open agent-UI protocol. Any AG-UI agent works — LangGraph, CrewAI, Mastra, Pydantic AI, Google ADK — write the agent once, and it shows up in every channel. And "shows up" means more than posting text: the agent streams responses, calls tools, handles files, renders real platform-native UI like Slack Block Kit, and can pause mid-task to wait for human approval in the thread.
This attacks the most underrated problem in the agent stack: distribution. The industry keeps building agents that live in their own tabs, then wondering why nobody forms a habit around tab number forty-one. The users are already in Slack and Teams all day; the agent should commute to them. Until now, doing that meant hand-writing a bot per platform, wrestling each one's UI framework, and rebuilding approval flows from scratch — which is why so few teams bothered.
There is also a quiet protocol angle. MCP standardized how agents reach tools; AG-UI plus Channels is a bid to standardize how agents reach people. If it sticks, the chat platforms become the browser of the agent era — the neutral surface where everyone's agents render — and the framework that owns that rendering layer sits in a very good spot.
← Back to all articles
The key design choice is that it builds on AG-UI, CopilotKit's open agent-UI protocol. Any AG-UI agent works — LangGraph, CrewAI, Mastra, Pydantic AI, Google ADK — write the agent once, and it shows up in every channel. And "shows up" means more than posting text: the agent streams responses, calls tools, handles files, renders real platform-native UI like Slack Block Kit, and can pause mid-task to wait for human approval in the thread.
This attacks the most underrated problem in the agent stack: distribution. The industry keeps building agents that live in their own tabs, then wondering why nobody forms a habit around tab number forty-one. The users are already in Slack and Teams all day; the agent should commute to them. Until now, doing that meant hand-writing a bot per platform, wrestling each one's UI framework, and rebuilding approval flows from scratch — which is why so few teams bothered.
There is also a quiet protocol angle. MCP standardized how agents reach tools; AG-UI plus Channels is a bid to standardize how agents reach people. If it sticks, the chat platforms become the browser of the agent era — the neutral surface where everyone's agents render — and the framework that owns that rendering layer sits in a very good spot.
Comments