copilotkit

Run npx [email protected] verify --json first to check wiring before manual debugging. Then inspect the /api/copilotkit route, installed v2 runtime code, and AG-UI event flow while preserving auth and rate-limit behavior.

The CopilotKit action or tool render name must match the Mastra tool-map key, not a createTool() id. Verify the tool-action name mapping, AG-UI result handling, and the rendered browser path rather than relying on tool unit tests alone.

v2 is current and imports from the /v2 subpath such as @copilotkit/react-core/v2. The package root is the deprecated v1 surface that still resolves, so mixing them fails silently at runtime instead of at import time.

No. Check the installed package version and pinned official sources first, because latest-main examples may use APIs that differ from 1.55.2. Preserve the v2 import surface and same-origin runtime contract when adapting examples.

The verify command does not cover tool execution, event ordering and streaming, or state synchronization. A passing wiring check must be followed by targeted tests and browser evidence for tool results and rendered generative UI.

CopilotKit owns the browser-facing transport, provider, and tool registration boundary. Agent definitions, tool implementations, workflows, memory, persistence, and HITL semantics belong to the Mastra skill, and product-domain rules belong to domain skills.