copilotkit-upgrade

Automate CopilotKit application migration from version 1 to version 2.

41|47|Updated May 8, 2026
One-click install
npx skills add https://github.com/jerelvelarde/Generative-UI-Global-Hackathon-Starter-Kit --skill copilotkit-upgrade-jerelvelarde
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copilotkit-upgrade
Source: https://github.com/jerelvelarde/Generative-UI-Global-Hackathon-Starter-Kit/tree/main/.cursor/skills/copilotkit-upgrade
Command: npx skills add https://github.com/jerelvelarde/Generative-UI-Global-Hackathon-Starter-Kit --skill copilotkit-upgrade-jerelvelarde

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires copilotkit, mcp-use, langchain, gemini, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill simplifies the migration process from CopilotKit v1 to v2, providing automated updates, breaking change mapping, and live documentation.

Core Features & Use Cases

  • Automated Migration: Automatically updates package imports, replaces deprecated hooks and components, and resolves breaking API changes.
  • Live Documentation: Includes an MCP server with tools for querying live CopilotKit documentation and source code.
  • Use Case: If you're using an application built with CopilotKit v1 and need to upgrade to v2, this Skill can help automate the migration process, reducing manual effort and potential errors.

Quick Start

Run the copilotkit-upgrade skill to begin the migration process for your CopilotKit v1 application.

Frequently Asked Questions about copilotkit-upgrade

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

FAQPage Schema
How do I migrate my CopilotKit application from v1 to v2?

To migrate CopilotKit from v1 to v2, you can automate the process to update package imports, replace deprecated hooks and components, and resolve breaking API changes. This automation reduces manual effort and potential errors during the upgrade.

What breaking changes are addressed when upgrading CopilotKit to v2?

Upgrading CopilotKit to v2 addresses breaking API changes by automatically updating package imports and replacing deprecated hooks and components. This ensures your application aligns with the v2 API reference and source code.

Can I query live CopilotKit documentation during the migration process?

Yes, you can query live CopilotKit documentation using an included MCP server with tools for querying live API references and source code. This provides accurate documentation alongside the automated migration process.

Do I need specific dependencies installed to automate CopilotKit migration?

Yes, automating CopilotKit migration requires CopilotKit and related dependencies such as langchain, gemini, and mcp-use to be installed. These packages enable the automated updates and live documentation features.

What is the best way to handle deprecated CopilotKit hooks and components?

The best way to handle deprecated CopilotKit hooks and components is to use an automated migration tool that maps and replaces them with v2 equivalents. This resolves breaking changes without manual intervention.

Why does my CopilotKit v1 application break after updating packages?

Your CopilotKit v1 application breaks after updating packages due to breaking API changes and deprecated features in v2. Running an automated migration skill maps these changes and updates package imports to resolve the errors.