# Channels

> Run one AG-UI agent in Slack, Microsoft Teams, and more through cloud-hosted Intelligence connections.

## Start with your coding agent [#start-with-your-coding-agent]

Copy this prompt into your coding agent to choose a framework, set up your agent,
and connect it to Slack or Microsoft Teams with CopilotKit Intelligence.
Prefer to work through the setup yourself? Follow the guides below.

<ChannelsStartPrompt />

Channels brings your agent into the conversations where work already happens.
Your agent still runs in your infrastructure. CopilotKit Intelligence owns the
Slack or Microsoft Teams connection, delivers each turn to your
Channels SDK listener, and sends the response back as native channel UI.

## How Channels connects your agent [#how-channels-connects-your-agent]

Channels connects the agent and application logic you run to the provider
connection managed by CopilotKit Intelligence. The diagram shows the boundaries
between those systems and the path each message takes.

<ImageZoom
  src="/images/channels/channels-architecture-light.png"
  alt="Channels architecture showing agent frameworks connected through AG-UI and the CopilotKit Runtime to the Channels SDK, with the channel runner — CopilotKit Intelligence's managed runner or your own — connecting to Slack, Microsoft Teams, WhatsApp, Discord, and more."
  width={4000}
  height={2608}
  className="block dark:hidden my-8 w-full rounded-xl"
/>
<ImageZoom
  src="/images/channels/channels-architecture-dark.png"
  alt="Channels architecture showing agent frameworks connected through AG-UI and the CopilotKit Runtime to the Channels SDK, with the channel runner — CopilotKit Intelligence's managed runner or your own — connecting to Slack, Microsoft Teams, WhatsApp, Discord, and more."
  width={4000}
  height={2400}
  className="hidden dark:block my-8 w-full rounded-xl"
/>

As explained in the [CopilotKit Intelligence overview](/slack/intelligence/overview),
CopilotKit open source runs without durable data. Features that need durable
data, such as databases and the state in them, are part of CopilotKit
Intelligence. A channel runner needs durable data to run correctly in
production: simultaneous participants, race conditions, retries, and delivery
guarantees all depend on it. CopilotKit Intelligence provides the managed
channel runner. You can build your own channel runner on the open-source
Channels SDK. You then implement the durable-data layer yourself.

<OpsPlatformCTA
  variant="inline"
  title="More channels are on the way"
  body="Slack and Microsoft Teams are generally available on cloud-hosted Intelligence. Direct SDK adapters also support Teams, Discord, and WhatsApp."
  ctaLabel="Book time with an engineer"
  surface="docs_channels_more_channels_contact"
  href="https://copilotkit.ai/talk-to-an-engineer"
  analyticsEvent="talk_to_us_clicked"
/>

Each message moves through the same five stages:

1. A person messages your app in Slack or Teams.
2. CopilotKit Intelligence receives the platform event using the credentials
   configured for that Channel.
3. A persistent Intelligence gateway connection delivers the turn to your
   long-running Channels SDK process.
4. The SDK runs your agent over [AG-UI](/agentic-protocols/ag-ui), executes
   channel tools, and renders the response.
5. Intelligence sends the result back as native Slack Block Kit or Teams
   Adaptive Card content.

This split keeps platform credentials out of your agent process without moving
your agent, tools, or business logic into CopilotKit.

| You run                                | CopilotKit Intelligence manages               |
| -------------------------------------- | --------------------------------------------- |
| The agent and its model credentials    | Slack and Teams platform credentials          |
| A long-running Channels SDK listener   | Platform ingress and credentialed delivery    |
| Tools and approval business logic      | Runtime registration, health, and reconnects  |
| Deployment, logs, and application auth | Conversation-history delivery to the listener |

## Production self-hosting: Run CopilotKit Intelligence in your own infrastructure [#production-self-hosting-run-copilotkit-intelligence-in-your-own-infrastructure]

Production self-hosting keeps your Channels configuration, provider credentials,
delivery state, and platform operations inside your network, giving your
organization control over data residency, security, and infrastructure.
You can fully self-host the Channels SDK. To run Intelligence in your own
Kubernetes cluster, follow
[Self-host CopilotKit Intelligence](/slack/intelligence/self-hosting).
<DocsTrackedLink href="https://copilotkit.ai/talk-to-an-engineer" surface="docs_channels_self_hosting_contact">Book time with a CopilotKit engineer</DocsTrackedLink>.

## Next step [#next-step]

Continue to [Configure the Channel in Intelligence](/slack/intelligence) to
create the managed Slack connection.

To post an app component as an image, see [Posting JSX as images](/slack/posting-jsx-as-images).
