CopilotKit Intelligence
CopilotKit Intelligence adds persistent Rich Threads, messaging Channels, memory, analytics, and automatic learning. Import supported LangGraph and Google ADK history, then synchronize future CopilotKit runs.
What is CopilotKit Intelligence?#
CopilotKit Intelligence is CopilotKit's production layer for persistent Rich Threads, memory, analytics, automatic learning, and messaging Channels. It sits beside your CopilotKit runtime and gives production agentic applications shared infrastructure without changing the frontend SDK, AG-UI protocol, or agent framework you use.
Start here when you are deciding what the platform gives you and where it should run. The rest of the Intelligence docs are deeper dives into the specific feature or hosting path you choose.
Ready to connect an existing app? Follow the CopilotKit Intelligence quickstart to store and inspect your first thread.
See this in Inspector
Open Inspector on localhost. Go to Learning. Review published Skills, their supporting Insights, and the Thread evidence behind each pattern. Inspector also shows when new Threads are ready for a Learning run; start runs and review Skill candidates in the Intelligence web app.
More detail: Inspector.
What the platform adds#
| Capability | What it gives you | Deeper dive |
|---|---|---|
| Durable threads and persistence | Resumable conversations that survive reloads, devices, and browser sessions. | Threads and Threads & Persistence Architecture |
| Existing conversation history | Import supported LangGraph threads or Google ADK sessions as Rich Threads, then synchronize future CopilotKit-mediated runs. | LangGraph history and Google ADK history |
| Channels | Run your agent in messaging channels through managed Intelligence connections. Managed Slack is available now; managed Teams is a controlled integration target. | Slack and Microsoft Teams |
| Memory | Durable facts and preferences that can be recalled across conversations. | Memories & Recall |
| Analytics | See what your agents do and where users get value, from the same interaction data. | Analytics |
| Automatic learning | Agents improve from real usage. No fine-tuning pipeline required. | Learning and Automatic skill delivery |
| Cloud-hosted Intelligence features | Projects, project API keys, conversation history, thread inspection, and plan management. | Cloud-hosted CopilotKit Intelligence |
| Platform-gated UI capabilities | Platform-gated UI surfaces such as Fully Headless Chat UI. | Fully Headless Chat UI |
| Self-hosting | The same platform running inside your own Kubernetes cluster, VPC, or data boundary. | Self-host CopilotKit Intelligence |
What you can add next
Rich Threads
Keep messages, generative UI, and tool activity across reloads and devices.
Open the Rich Threads guideChannels
Run your agent in Slack through managed Intelligence connections. See the guide for Teams availability and other channel adapters.
Open the Channels guideMemory
Carry durable facts and preferences across conversations without tying them to one thread.
Open the Memory guideAnalytics
See what your agents do and where users get value, from the same interaction data.
See Analytics on the product pageAutomatic Learning
Agents improve from real usage. No fine-tuning pipeline required.
Open the Learning guideSelf-hosting
Run the same platform in your own cluster, VPC, or data boundary.
Open the self-hosting guideFollow the Intelligence quickstart to connect your runtime and confirm threads work.
Open the Intelligence quickstart
Already have conversations in LangGraph or Google ADK?#
If you are adding a user-facing app to an agent that already has conversation history, you do not need to start with an empty thread list. Import supported history into CopilotKit Intelligence as Rich Threads, then let users open and continue those conversations in your CopilotKit app.
- Import LangGraph threads from LangGraph Server, LangGraph Platform, or LangSmith Deployment thread and run APIs. Standalone LangChain message stores, LangSmith traces, and embedded checkpointers without those APIs are not supported import sources.
- Import Google ADK sessions from database session stores or Vertex/Agent Engine session history. In-memory sessions cannot be exported.
Historical import is a one-time operation, not a continuous mirror of every change in your source store. Future CopilotKit-mediated runs synchronize with Intelligence and continue through your framework's native persistence path when it remains configured with durable storage. Follow your framework's guide for agent mapping and thread continuity.
Hosting options#
| Option | Choose it when | What you operate |
|---|---|---|
| Cloud-hosted CopilotKit Intelligence | You want CopilotKit to run the platform for you: hosted projects, API keys, thread history, dashboard inspection, and plan management. | Your app, your runtime, your agent, and your model provider credentials. |
| Self-host CopilotKit Intelligence | You need the platform inside your own VPC, Kubernetes cluster, data residency boundary, or enterprise operations model. | The copilot-intelligence Helm release, Postgres, Redis, ingress, OIDC, secrets, upgrades, and monitoring. |
Both options use the same CopilotKit application surface. Your frontend still uses CopilotKit APIs, your runtime still speaks AG-UI, and your agents keep the same framework integration. The deployment choice changes the platform endpoint and credentials your runtime uses.
Plans and access#
The cloud-hosted version includes self-service plans for individual developers and teams, plus the Enterprise Intelligence tier for larger deployments. You manage cloud-hosted plans in the web app.
Self-hosted access is available on the Team self-hosted plan or a custom Enterprise plan. Use it when you have a concrete compliance, residency, network, or platform-operations requirement that makes a hosted service the wrong fit.
Which page should I read next?#
| Goal | Read this |
|---|---|
| Decide what the platform includes | Stay on this overview. |
| Connect an app to hosted projects and API keys | Cloud-hosted CopilotKit Intelligence |
| Run the platform in your own cluster | Self-host CopilotKit Intelligence |
| Understand the runtime/platform architecture | CopilotKit Intelligence architecture |
| Add persistent conversations to an app | Threads |
| Let users open existing LangGraph conversations in a CopilotKit app | Synchronize LangGraph Threads |
| Bring existing ADK session history into a CopilotKit app | Synchronize ADK Threads |
| Make an agent available in Slack or Microsoft Teams | Slack and Microsoft Teams, including provider availability |
| Give an agent durable context across conversations | Memories & Recall |
| Turn real usage into reusable agent behavior | Learning and Automatic skill delivery |
| Understand thread replay and realtime sync | Threads & Persistence Architecture |
FAQs#
Does my application code change between hosting options?#
No. Your frontend UI, CopilotKit runtime, and agent integration stay focused on CopilotKit APIs. The deployment mode changes which platform URL and credentials your runtime uses.
What is the difference between a project API key and a license key?#
A project API key connects your runtime to one cloud-hosted CopilotKit Intelligence project. A license key unlocks self-hosted CopilotKit Intelligence capabilities and does not require runtime traffic to go through the cloud-hosted service.
Can I start cloud-hosted and move to self-hosted later?#
Yes. The application integration is intentionally the same. Moving from cloud-hosted projects to self-hosting is available on the Team self-hosted plan or a custom Enterprise plan. Plan the migration around data movement, identity, network endpoints, and operational ownership rather than a frontend rewrite.