Provider setup and permissions
Coordinate app credentials, callbacks, workspace installs, identity, and approval boundaries for every channel.
Channels
Agents in Slack, Teams, and more without the production headaches.
Start with the open-source Channels SDK to connect your agent to Slack and Microsoft Teams. Add CopilotKit Enterprise Intelligence for durable state, reliable delivery, and production operations.
Early access
Get early access to Channels.
Share what your team wants to build and we'll send updates as Channels opens more broadly. Need guidance on architecture, rollout, or deployment? Talk to an engineer.
Production friction
Building the agent is easy. Bringing it into production channels? Not so much.
A working agent is only the beginning. Each channel adds provider setup, identity, durable state, and delivery concerns that teams have to solve before real work can depend on it.
Durable channel state
Keep provider conversations mapped to the right agent threads so resumes, approvals, and updates land correctly.
Reliable delivery and operations
Handle retries, realtime transport, background work, and delivery visibility before a pilot becomes critical infrastructure.
One stack, two layers
Start with the Channels SDK. Add CopilotKit Enterprise Intelligence for production.
Use the open-source foundation directly in your customer-owned runtime, then add the stateful production layer when your rollout needs durable operations.
Foundation · open source
Channels SDK
The open-source, direct integration layer for bringing an existing CopilotRuntime or AG-UI agent into supported channels. Your team runs this path in the runtime you own.
- Own and run your agent and runtime
- Control provider credentials, ingress, egress, and deployment
- Choose storage and operating patterns for your application
- Start stateless for prototypes and initial releases
Production layer · stateful
CopilotKit Enterprise Intelligence
The stateful production layer for Channels, deployed through CopilotKit-managed cloud or self-hosted in your infrastructure and connected to your agent and runtime.
- Durable canonical threads and channel state
- Managed provider setup, credentials, delivery, and retries
- Realtime transport, provider egress, and background compute
- Operational visibility for production rollouts
Channel architecture
One agent architecture, native to every supported channel.
Channels carries structured interactions between your runtime and each collaboration surface, so you can expand reach without rebuilding the agent.
Channels
CopilotKit+
One structured agent-user interaction layer across every channel.
Early access: Slack · Microsoft TeamsPlanned: Discord · Google Chat
Native channel experiences
Agent work that belongs inside the conversation.
Stream replies, render channel-native cards, request approvals, and update work in place. Structured events preserve the agent interaction instead of flattening it into another transcript.
Slack thread
# revenue-ops
Summarize pipeline risk and prep the renewal handoff.
I found three at-risk accounts and generated the handoff below.
Generated workflow UI
Pipeline health
Renewals
$1.8M
At risk
3
Next steps
7
Slack
A first-class Slack experience.
Map mentions, direct messages, channel conversations, and commands to the right agent interaction. Return streamed replies, Block Kit-style UI, approvals, and workflow updates where the team is already coordinating.
- Connect Slack events and thread metadata to the right agent request.
- Render native cards, forms, summaries, and approval controls.
Microsoft Teams
Enterprise workflows that stay native to Teams.
Map Teams conversations and Microsoft Teams activity events into structured agent interactions. Render Adaptive Cards, live updates, and approval steps without asking users to leave the channel.
- Connect Teams conversations and events to durable agent interactions.
- Render generated UI, tool results, and approvals through Adaptive Cards.
Production workflow
Configure, deploy, done.
CopilotKit Enterprise Intelligence gives teams one guided path from provider setup to a production Channels rollout, with the operating model and visibility each organization needs.
- 1
Configure
Connect the channel provider.
Set up provider credentials, callbacks, and install details through one guided Channel Setup flow.
- 2
Deploy
Choose the operating model.
Use CopilotKit-managed cloud or self-host CopilotKit Enterprise Intelligence in your own infrastructure.
- 3
Operate
Keep the rollout visible.
Track canonical state, delivery health, and channel readiness from the Operational Workspace.
Channel Setup
Move from provider configuration to an install-ready Slack handoff.
Operational Workspace
Review channel setup, delivery health, and rollout state in one place.
Use cases
Put agents where decisions are already moving.
Channels works best when the conversation is part of the workflow, not just another place to ask a question.
Incident triage
Bring the right agent into an active channel to gather context, suggest next steps, and keep responders aligned.
Support escalation
Carry customer context into the escalation thread and give specialists structured actions without another dashboard.
Internal operations
Let teams request updates, launch workflows, and review results in the channel where the work is coordinated.
Approvals and reporting
Render reviewable summaries and approval controls, then return the result to the same durable conversation.
FAQ
Channels, ownership, and the production boundary.
Start with the open-source SDK in your runtime, then add CopilotKit Enterprise Intelligence in managed cloud or your own infrastructure when you need the production layer.
What are Channels?
Channels are the user-facing places where your existing agent can join the work. Slack and Microsoft Teams are available in early access; Discord and Google Chat are planned. The same agent and tools stay behind every channel.
What is the Channels SDK?
The Channels SDK is the open-source, direct integration layer. Your team owns the agent, runtime, provider credentials, deployment, ingress, egress, and storage choices.
What does CopilotKit Enterprise Intelligence add?
It adds the stateful and operational production layer: canonical threads and channel state, reliable delivery, realtime transport, managed provider setup, background compute, and operational visibility.
How can CopilotKit Enterprise Intelligence be deployed?
CopilotKit Enterprise Intelligence is available as a CopilotKit-managed cloud service or as a self-hosted deployment in your own infrastructure. The deployment model changes who operates the Intelligence infrastructure, not the core product experience.
Bring your agent to the work
Start building for Channels without taking on every production edge case.
Join early access or talk through the right SDK and deployment path for your team.
