Show HN: The Channels SDK – Bring Any Agent to Any Channel (Slack, MS Teams) | AI Paper Digest

TL;DR Highlight

Bring any AG-UI agent to Slack and Teams with native interactive UI, keeping your agent code

Who Should Read

A backend developer who wants an existing LangGraph or Mastra agent to work inside company Slack or Teams

Core Mechanics

Keep your agent, add the chat layer
- Your agent's tools, model, and business logic stay unchanged.
- Any agent compatible with AG-UI (a protocol linking agents to UIs) can connect.
Write the UI once
- Describe a message once and it renders as Slack Block Kit or Teams Adaptive Cards.
- You can put buttons, choices, and approval gates in the conversation.
Let your coding agent do the setup
- Running npx copilotkit@latest channels setup installs a skill and copies a prompt to your clipboard.
- Paste it into your coding agent and it asks for your platform and agent framework.
Manual setup needs Node 22+
- Install @copilotkit/channels and @copilotkit/runtime together and upgrade them together.
- You need a long-running Node process or container.
Responsibilities are split

Community Reactions

Licensing was questioned
- One commenter said only the client is MIT while the service that runs it is closed and license-gated.
- The team replied that Intelligence can be self-hosted, makes no outside calls, and your agent makes the model calls.
Internal dogfooding stories
- Team members said that using it internally led to many small task-specific agents in their channels.
- Examples were a lunch-order bot, incident triage, and a PR-to-marketing-video bot.
Architecture explanation
- A comment explained the ack-first loop: post the approval card, ack delivery, and resume when the click arrives.
- Handler IDs are content hashes, so buttons from last week still work after a deploy.
Pricing concerns and alternatives
- One commenter said they dropped the idea after seeing Team pricing.
- Others asked if it wraps Vercel's Chat SDK, and one said eve.dev worked well for them.

How to Apply

Spin up a Slack bot with the setup command today
- Run npx copilotkit@latest channels setup and paste the clipboard prompt into your coding agent.
- Pick a test Slack workspace and enter secrets into .env yourself.
Check whether your agent is AG-UI compatible
- Look in the AG-UI integrations docs for your framework (LangGraph, Mastra, CrewAI, etc.).
- If supported, swap the makeAgent factory for your own agent.
Add approval buttons before write actions
- Put an approval gate before hard-to-undo tool calls like creating issues or editing a DB.
- Follow OpenTag's approval flow for Linear and Notion writes.
Verify licensing and pricing before adopting
- Check how Intelligence is hosted and the Team plan pricing before rolling it out.
- Ask CopilotKit directly about self-hosting.

Try It

copy & run

# Paste into a coding agent like Claude Code (first run npx copilotkit@latest channels setup in your shell)

Read https://copilotkit.ai/channels-guide.md and help the user build their first channel.

My agent framework: {{LangGraph / Mastra / CrewAI / built-in agent}}
Platform: {{Slack or Microsoft Teams}}

If you have no browser tool, ask me to add one first. I'll type the secrets myself.

Next: mention the bot in a channel and check for a thread reply, then ask the agent to add an approval button.

Terminology

AG-UIA protocol for agents to talk to user interfaces. Agents that follow it plug into any front end, like a USB port.

Block Kit / Adaptive CardsThe native message UI formats of Slack and Teams. It is like writing the same screen in each platform's own language.

AdapterA translator that turns each platform's webhooks into one neutral event shape.

Ack-firstPost the approval card and acknowledge delivery first, then resume the run when the click arrives. It's like confirming a package receipt before opening it.

CopilotKit IntelligenceThe backend layer that handles platform connection, delivery, reconnects, threads, and memory.

Show HN: The Channels SDK – Bring Any Agent to Any Channel (Slack, MS Teams)