copilotkit-integrations

Connects external agent frameworks to CopilotKit applications via the AG-UI protocol.

Updated May 9, 2026
One-click install
npx skills add https://github.com/franciscogar94/CrisisOS --skill copilotkit-integrations-franciscogar94
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: copilotkit-integrations
Source: https://github.com/franciscogar94/CrisisOS/tree/main/.cursor/skills/copilotkit-integrations
Command: npx skills add https://github.com/franciscogar94/CrisisOS --skill copilotkit-integrations-franciscogar94

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Wiring a backend agent framework like LangGraph, CrewAI, or PydanticAI into a CopilotKit frontend requires matching the correct AG-UI adapter, client class, server endpoint, and port for each framework, and getting any of these wrong breaks the streaming connection between agent and UI. ## Core Features & Use Cases - Framework Decision Tree: Routes you to the correct integration guide based on language (Python, TypeScript, .NET) and framework (LangGraph, CrewAI, PydanticAI, Mastra, ADK, LlamaIndex, Agno, Strands, Microsoft Agent Framework, A2A). - Per-Framework Reference Guides: Detailed integration docs covering agent definition, FastAPI server setup, Next.js route configuration, and shared state patterns for each supported framework. - Common AG-UI Patterns: Ready-to-use snippets for CopilotKitProvider, useAgent shared state, useFrontendTool, useRenderToolCall generative UI, and useHumanInTheLoop approval flows. - Use Case: You have a LangGraph Python agent and need it to drive a React canvas. The skill directs you to the langgraph.md reference, where you wrap the graph with LangGraphAGUIAgent, serve it via add_langgraph_fastapi_endpoint on port 8123, and connect it in route.ts with LangGraphHttpAgent. ## Quick Start Ask the agent to connect your LangGraph Python agent to a CopilotKit Next.js frontend using the AG-UI protocol.

Frequently Asked Questions about copilotkit-integrations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect a LangGraph agent to CopilotKit?▼

Wrap your compiled graph with LangGraphAGUIAgent and serve it via add_langgraph_fastapi_endpoint on port 8123. In the Next.js route, create a LangGraphHttpAgent from @copilotkit/runtime/langgraph pointing at that URL and register it in CopilotRuntime.

Which AG-UI client class should I use for my agent framework?▼

LangGraph self-hosted uses LangGraphHttpAgent, LangGraph Platform uses LangGraphAgent, CrewAI Crews use CrewAIAgent, Mastra uses MastraAgent, and LlamaIndex uses LlamaIndexAgent. Most other Python frameworks including ADK, PydanticAI, Agno, and Strands use the generic HttpAgent from @ag-ui/client.

Does CopilotKit support TypeScript agent frameworks?▼

Yes. Mastra agents run in-process via MastraAgent.getLocalAgents with no separate server, and LangGraph JS agents use CopilotKitStateAnnotation with convertActionsToDynamicStructuredTools from @copilotkit/sdk-js/langgraph. Other TypeScript agents can connect through the generic HttpAgent.

How do I share state between my agent and the CopilotKit frontend?▼

Agents emit STATE_SNAPSHOT events that the frontend receives through the useAgent hook. Each framework handles this differently: LangGraph extends CopilotKitState, PydanticAI returns StateSnapshotEvent from tools, and Strands uses state_from_args in ToolBehavior config.

Can I orchestrate multiple agents from different frameworks in one CopilotKit app?▼

Yes, using A2AMiddlewareAgent from @ag-ui/a2a-middleware. It wraps an orchestrator agent, registers the URLs of specialized A2A-compatible agents, and injects a send_message_to_a2a_agent tool so the orchestrator can delegate tasks across frameworks.