copilotkit-cli

Diagnose and scaffold CopilotKit projects using the npx copilotkit CLI commands.

1|Updated Sep 15, 2026
One-click install
npx skills add https://github.com/amoai-tech/mdeai --skill copilotkit-cli-amoai-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copilotkit-cli
Source: https://github.com/amoai-tech/mdeai/tree/main/.claude/skills/copilotkit/references/official/copilotkit-cli
Command: npx skills add https://github.com/amoai-tech/mdeai --skill copilotkit-cli-amoai-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging a CopilotKit integration by hand means manually checking API keys, runtime endpoints, CORS origins, and package versions. This Skill replaces that survey with the verify command, which probes up to eleven wiring checks in one run and names exactly which URL it tested and where that URL came from. ## Core Features & Use Cases - Wiring Verification: Run verify --json to check hosted project selection, API key validity, runtime responses, agent declaration, thread routes, CORS preflight, and package version alignment, with chained failures pointing to the first real problem. - Project Scaffolding and Onboarding: Use init (alias create) to scaffold a new starter app, or onboard start for agent-guided integration into an existing repository. - Authentication and Project Selection: Sign in with login --json for agent-driven flows, then use project select to record a hosted Intelligence project and provision the CPK_INTELLIGENCE_API_KEY runtime key. - Use Case: Your CopilotKit chat UI renders but the agent never responds. Run npx [email protected] verify --frontend-url http://localhost:3000 --round-trip to find whether the failure is the credential, the runtime, or the CORS origin before touching any code. ## Quick Start Ask the assistant to run the CopilotKit verify command against your project and report which wiring check fails first.

Frequently Asked Questions about copilotkit-cli

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

FAQPage Schema
How do I debug a CopilotKit app that is not working?

Run npx [email protected] verify --json before any manual debugging. It checks the hosted project, API key, runtime, agent declaration, thread routes, and package versions, and the first failing check is the real problem since later checks chain on earlier ones.

How do I add CopilotKit to an existing application?

Run npx [email protected] onboard start inside your repository. It launches an agent-guided flow with checkpoints and proof steps rather than a scaffold, and --intent <feature> targets one feature on an app that already has CopilotKit.

What does the CopilotKit verify command check?

Verify checks up to eleven things: hosted project selection, API key presence and authentication, runtime response and agent declaration, thread routes, frontend assets, CORS origin acceptance, and installed package version alignment. It also reports the runtime version, agent framework, and license state.

Can I use the CopilotKit CLI with a self-hosted runtime?

Yes, pass --expect-runtime oss to verify for a self-hosted runtime without Intelligence. It exits zero only when /info declares the named agent, reports no Intelligence entitlement, and --round-trip --agent <id> passes.

What does verify not cover in CopilotKit debugging?

Verify does not test tool execution, event ordering, streaming behavior, or state synchronization. The --round-trip flag deliberately asks a question needing no tools, so use the Inspector for runs that stall mid-stream or never finish.

Where does the CopilotKit CLI store the project API key?

The project select command writes CPK_INTELLIGENCE_API_KEY=cpk_... into .env and records the choice in .copilotkit/project.json. It is a server-side runtime key, so it takes no NEXT_PUBLIC_ or VITE_ prefix.