⚡ CopilotKit Channels SDK
Slack & Teams in 15 Minutes
Stop wrestling with OAuth and webhooks. Get your agent live before your coffee cools.
Join 500+ developers · No spam, just the template.
Why Channels SDK Matters Right Now
The CopilotKit team just released their Channels SDK, and the developer response on Hacker News (86 points, 20 comments) shows real appetite for bringing agents into Slack and Teams. But the official examples are minimal — they show a demo, not a production path. Developers are left to piece together OAuth flows, event subscriptions, and message formatting on their own, which turns a 15-minute job into a two-day slog.
Existing solutions like LangChain's Slack integration require you to buy into a whole different ecosystem, and they still don't handle the channel-specific quirks. The truth is, most teams just want their CopilotKit agent to show up in a channel and start working. That's exactly what this starter kit does — it wraps the official SDK with a clean, reusable structure so you skip the grunt work.
The timing is perfect: the SDK is brand new, the ecosystem is wide open, and early adopters are actively searching for ways to get started. With the Channels SDK Starter, you're not just keeping up — you're shipping while the iron is hot.
How It Works
Clone the template
Grab the GitHub repo with a single command. You get a complete TypeScript project with Slack and Teams folders, pre-configured environment variables, and a docker-compose file for local development.
Add your tokens
Drop in your Slack bot token and Teams app credentials. The starter handles OAuth, event subscriptions, and webhook routing automatically — no need to read 50 pages of API docs.
Run & deploy
Start locally with docker-compose, test with ngrok, then deploy to your favorite host. Your CopilotKit agent is now live in Slack and Teams — fully functional, with message formatting and error handling built in.
What You Get
15-minute setup
A complete engineering template, not a toy example. You get production-ready code with proper error handling, logging, and reconnection logic — the boring parts are already done for you.
Zero config pain
OAuth, event subscriptions, and message format conversion are all wrapped and handled. You don't need to understand Slack's block kit or Teams' adaptive cards — just plug in your agent.
Dual-channel coverage
One codebase for both Slack and MS Teams. Write your agent logic once, and the starter handles the channel-specific adapters. Save days of duplicated work and keep your codebase clean.