copilotkit-upgrade

Migrate CopilotKit v1 applications to the v2 AG-UI protocol architecture.

Updated May 9, 2026
One-click install
npx skills add https://github.com/hanu-tayal/agentic-interfaces-hackathon --skill copilotkit-upgrade-hanu-tayal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copilotkit-upgrade
Source: https://github.com/hanu-tayal/agentic-interfaces-hackathon/tree/main/.cursor/skills/copilotkit-upgrade
Command: npx skills add https://github.com/hanu-tayal/agentic-interfaces-hackathon --skill copilotkit-upgrade-hanu-tayal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the complex migration from CopilotKit v1 to v2 by providing a structured path to update package imports, replace deprecated hooks, and transition to the AG-UI protocol.

Core Features & Use Cases

  • API Mapping: Automatically identifies deprecated v1 hooks like useCopilotAction and provides the v2 equivalent, useFrontendTool.
  • Protocol Transition: Guides the shift from GraphQL-based runtimes to the new AG-UI SSE-based protocol.
  • Dependency Management: Provides a clear roadmap for consolidating fragmented React packages into the unified @copilotkit/react package.

Quick Start

Use the copilotkit-upgrade skill to audit my current codebase and generate a migration plan for moving from v1 to v2.

Frequently Asked Questions about copilotkit-upgrade

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

FAQPage Schema
How do I migrate CopilotKit v1 to v2?

Migrating CopilotKit v1 to v2 requires refactoring codebases to replace deprecated hooks like useCopilotAction with useFrontendTool, consolidating fragmented React packages into @copilotkit/react, and transitioning runtimes to the AG-UI streaming protocol.

What is the AG-UI protocol in CopilotKit v2?

The AG-UI protocol is a modern streaming event-based communication architecture that replaces the legacy GraphQL-based runtimes in CopilotKit v1, utilizing SSE-based communication to maintain agentic functionality.

How do I replace deprecated CopilotKit v1 hooks?

To replace deprecated CopilotKit v1 hooks, map legacy APIs such as useCopilotAction to their v2 equivalents like useFrontendTool, ensuring that agentic functionality is preserved during the refactoring process.

Can I consolidate CopilotKit React packages during v2 migration?

Consolidating CopilotKit React packages during v2 migration involves transitioning fragmented v1 dependencies into the unified @copilotkit/react package, streamlining dependency management while adopting the AG-UI protocol architecture.

Does CopilotKit v2 support GraphQL runtimes?

CopilotKit v2 does not use GraphQL-based runtimes; it transitions to the new AG-UI SSE-based protocol for streaming event-based communication, requiring endpoint reconfiguration during the v1 to v2 migration.

What are the limitations of migrating CopilotKit v1 to v2?

Migrating CopilotKit v1 to v2 requires comprehensive endpoint reconfiguration and hook replacement, meaning agentic functionality may be disrupted if the streaming event-based communication architecture is not fully adopted.