Channels SDK

The Channels SDK connects an agent to chat providers through a long-running @copilotkit/channels process. In the managed Slack and Microsoft Teams path, CopilotKit Intelligence owns the provider connection while your process owns the agent, tools, approvals, state, and deployment. The package also exports developer-operated direct adapters for Slack, Teams, Discord, Telegram, and WhatsApp.

API reference

<Cards> <Card title="createChannel" description="Declare a managed provider or developer-operated direct adapter and attach the Channel to CopilotRuntime." href="/reference/channels/functions/createChannel" icon={<LinkIcon />} /> <Card title="Channel" description="Configure managed or direct delivery, register handlers and tools, configure storage, and inspect the Channel declaration." href="/reference/channels/classes/Channel" icon={<LinkIcon />} /> <Card title="Thread" description="Post and update messages, run or resume the agent, read history, and manage conversation state." href="/reference/channels/classes/Thread" icon={<LinkIcon />} /> <Card title="StateStore" description="Persist workflow state, callback snapshots, transcripts, locks, deduplication, and queues." href="/reference/channels/types/StateStore" icon={<LinkIcon />} /> </Cards>

Classes

• Channel
• Thread
• MemoryStore
• Transcripts

Functions

• createChannel
• defineChannelTool
• defineChannelCommand
• bind
• renderToIR

Message components

• Message
• Header
• Section and Markdown
• Fields and Field
• Context
• Image and Divider
• Table, Row, and Cell
• Chart

Interactive components

• Actions
• Button
• Select
• Input
• Modal components — exported for direct adapters; unavailable on managed Slack and Teams
• JSX callbacks

Types

• IncomingMessage
• AgentContentPart
• InteractionContext
• MessageRef
• StoreConfig
• StateStore
• ChannelNode
• ActionStore — deprecated migration reference

Provider SDKs

• Direct provider adapters — public entry points, required options, and the boundary between managed and developer-operated delivery

Provider guides

Start with the provider and agent framework you are deploying:

• Connect and run your agent in Slack
• Connect and run your agent in Microsoft Teams

The provider picker in those guides keeps the same task and selected agent framework when you switch between Slack and Teams.