Show HN: The Channels SDK – Bring Any Agent to Any Channel ( | Coderz Club

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

Uh oh! There was an error while loading. Please reload this page. CopilotKit / channels-sdk Public Notifications You must be signed in to change notification settings Fork 45 Star 660 mainBranchesTagsGo to fileCodeOpen more actions menuFolders and filesNameNameLast commit messageLast commit dateLatest commit History49 Commits49 Commits.agents/skills/build-channels-agent.agents/skills/build-channels-agent .claude/skills.claude/skills assetsassets examplesexamples .gitignore.gitignore .gitmodules.gitmodules AGENTS.mdAGENTS.md LICENSELICENSE README.mdREADME.md View all filesRepository files navigation Channels SDK Bring any AI agent into Slack, Microsoft Teams, and the channels where work happens — with native, interactive UI. Try Channels · Build with the SDK · Explore OpenTag channels-sdk.demo.mp4 Your agent keeps its tools, model, and business logic. Channels gives it a native place to work with people. Your agent belongs where work happens Channels connects an AG-UI-compatible agent to the communication platforms your team already uses. The agent can understand the conversation, stream a response, call tools, work with files, render interactive UI, and pause for human approval. Bring your agent Render native UI Keep people in control Use CopilotKit's built-in agent or connect LangGraph, CrewAI, Mastra, Pydantic AI, Google ADK, and other AG-UI agents. Describe a message once and render it as native Slack Block Kit, Teams Adaptive Cards, and platform-specific UI. Put buttons, choices, and approval gates directly into the conversation before an agent acts. One interaction, native to every channel Slack Microsoft Teams Discord Channels is built for a world where the same agent can meet users across every communication surface. Managed connections for Slack and Microsoft Teams are available through CopilotKit Intelligence, with more channels on the way. Try it before you build it Experience a real Channels agent in Slack or Microsoft Teams without configuring an app, runtime, or provider credentials. Try Channels → Choose a platform, join the experience, and see how an agent handles context, tool use, and native channel UI. Build your first Channel Your agent and application logic run in your infrastructure. CopilotKit Intelligence manages the platform connection and delivers each turn to your long-running Channels process. Fastest path: let your coding agent drive Building a Channels agent spans a project, an agent, a managed Channel, a provider app, and a long-running runtime. One guide walks your agent through all of it. npx copilotkit@latest channels setup That installs the channels-setup skill, prints a prompt, and copies it to your clipboard. Paste it into your coding agent. The skill is a pointer — it fetches the workflow from copilotkit.ai/channels-guide.md when your agent needs it, so the steps are current even if the installed skill is months old. The guide asks which platform you want, Slack or Microsoft Teams, and which agent framework. Your agent drives the Slack and Intelligence consoles itself, in your own signed-in session. If it has no browser or computer-use tool yet, it will ask you to add one first — that is the intended path, not a fallback. You type the secrets; it does the clicking. Or install the Slack setup skill on disk Skip the hosted guide and put the Slack workflow directly in the coding agent you are already running in: npx copilotkit@latest skills install --skill setup-slack-channel -y -y installs that one skill without opening a picker. The skill is scoped to Slack — for Microsoft Teams, use the guide above. The CLI covers the Intelligence side: copilotkit channels add --adapter slack declares the Channel and attaches the adapter, and copilotkit channels status compares your configuration, your code, and the server. What stays in the browser is the provider side — creating the Slack app and installing it into a workspace — plus issuing the project API key. No CLI flag accepts a credential value, so the bot token and signing secret stay in your .env and with you. Unknown option '--skill'? An older copilotkit — globally installed or left in the npx cache — is shadowing the current CLI. Keep the @latest; that is what forces npx to fetch the current version instead of reusing what it already has. The steps below are the same path, done by hand. 1. Configure the connection Create a Channel in CopilotKit Intelligence and connect Slack. Keep the Channel Code and project-scoped Intelligence API key for the next steps. You need Node.js 22 or later and a long-running Node process or container. 2. Install the SDK npm install @copilotkit/channels @copilotkit/runtime npm install --save-dev tsx typescript @types/node npm pkg set type=module Channels and Runtime ship together as a tested pair. Upgrade both packages together. 3. Create the listener The example below uses CopilotKit's built-in agent. Replace makeAgent w