copilotkit-debug

To debug CopilotKit runtime connectivity issues, run `npm ls @copilotkit/*` to check version consistency across packages. This Skill uses error codes and event tracing to identify and resolve runtime connection problems efficiently.

CopilotKit agent problems with tool execution or state synchronization are diagnosed through event tracing and error code analysis. This Skill identifies connectivity failures and state sync mismatches within the CopilotKit agent architecture to restore proper tool execution.

Voice transcription errors in CopilotKit are resolved by addressing authentication failures and network issues. This Skill traces transcription-specific error codes to pinpoint whether the problem stems from invalid credentials or network connectivity disruptions.

Diagnosing CopilotKit runtime problems requires knowledge of CopilotKit architecture and runtime configuration. You need access to the project's npm environment to run package checks and inspect error codes and event traces for accurate troubleshooting.

The best way to troubleshoot CopilotKit package version conflicts is running `npm ls @copilotkit/*` to verify version consistency across all installed CopilotKit packages. Inconsistent versions often cause runtime connectivity failures and agent state synchronization errors.

When the CopilotKit runtime is not working, first check package version consistency using `npm ls @copilotkit/*`. Then use error codes and event tracing to isolate whether the failure is in runtime connectivity, agent tool execution, or voice transcription authentication.