copilotkit-upgrade

Migrate CopilotKit v1 applications to v2 with AG-UI runtime updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you upgrade a CopilotKit v1 application to v2 without guessing at renamed hooks, removed components, or the new AG-UI runtime architecture.

Core Features & Use Cases

  • API Migration: Replaces deprecated v1 hooks and components with their v2 equivalents, including provider, chat, tool, and interrupt APIs.
  • Runtime Modernization: Updates service-adapter-based runtime code to the new agent-based CopilotRuntime and Hono endpoint flow.
  • Use Case: Use it when a project still imports @copilotkit/react-core, @copilotkit/react-ui, or v1 runtime utilities and needs a reliable upgrade path.

Quick Start

Ask the Skill to inspect your CopilotKit codebase and produce the exact v1-to-v2 import, hook, component, and runtime changes needed for a safe migration.

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 hooks and components to v2?

To migrate CopilotKit v1 to v2, replace deprecated hooks, components, and types with their current equivalents. This includes updating provider, chat, tool, and interrupt APIs to align with the new v2 architecture for a safe codebase upgrade.

What changes are needed to upgrade CopilotKit runtime to AG-UI?

Upgrading CopilotKit runtime to AG-UI requires modernizing service-adapter-based code to the new agent-based CopilotRuntime and Hono endpoint flow, replacing the old GraphQL-based runtime endpoints with the updated architecture.

When do I need to upgrade my CopilotKit application to v2?

You need to upgrade CopilotKit to v2 when your project still imports @copilotkit/react-core, @copilotkit/react-ui, or v1 runtime utilities and requires moving to the current AG-UI runtime architecture.

Can I use CopilotKit v1 chat UI and frontend tools with the new runtime?

Yes, but v1 chat UI and frontend tools must be remapped to their v2 equivalents. The migration maps deprecated provider, chat, tool, and interrupt APIs to current replacements compatible with the agent-based runtime.

What are the limitations when migrating CopilotKit v1 applications?

The limitation is that unsupported v1-only features must be removed. The migration requires accurate package remapping, provider updates, and agent-based runtime configuration, necessitating careful removal of deprecated GraphQL flows.

Does CopilotKit v2 migration support agent contexts and interrupts?

Yes, CopilotKit v2 migration maps deprecated agent contexts and interrupt APIs to their current replacements, ensuring these features integrate correctly with the new AG-UI runtime and agent-based CopilotRuntime configuration.