Channels SDK
API reference for managed and direct provider agents built with @copilotkit/channels.
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.
npm install --save-exact @copilotkit/channels@0.6.1 @copilotkit/runtime@1.65.0API reference
createChannel
Declare a managed provider or developer-operated direct adapter and attach the Channel to CopilotRuntime.
Channel
Configure managed or direct delivery, register handlers and tools, configure storage, and inspect the Channel declaration.
Thread
Post and update messages, run or resume the agent, read history, and manage conversation state.
StateStore
Persist workflow state, callback snapshots, transcripts, locks, deduplication, and queues.
Classes
Functions
Message components
MessageHeaderSectionandMarkdownFieldsandFieldContextImageandDividerTable,Row, andCellChart
Interactive components
ActionsButtonSelectInputModal components— exported for direct adapters; unavailable on managed Slack and TeamsJSX callbacks
Types
IncomingMessageAgentContentPartInteractionContextMessageRefStoreConfigStateStoreChannelNodeActionStore— 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:
The provider picker in those guides keeps the same task and selected agent framework when you switch between Slack and Teams.