AgentKit · Support
AgentKit Troubleshooting
Quick checks when the ak CLI, Desktop App, or AgentKit runtime adapters misbehave — not the ClaudeKit troubleshooting surface.
CLI not found
Confirm the install directory is on PATH, open a new terminal, then run ak --version.
Quick diagnostics
doctor
ak doctor --json
ak doctor --json --offlineUninstall commands
ak uninstall ≠ remove a global kit
ak uninstall
Removes an AgentKit-managed project. Needs an AK project at/above cwd — not for removing a global kit.
ak kit uninstall <kit>
Removes AgentKit-owned kit content by scope/mode. Flags + full clean reinstall: clean reinstall .
Runtime
Skill not visible
- 1 Confirm the Kit installed for the correct runtime and scope (project vs global).
- 2 Restart the coding assistant or open a new session after install.
- 3 Use the correct runtime syntax (/ak:… vs $ak:…).
- 4 Read adapter warnings: a component may be dropped or kept as supporting content only.
Desktop
Desktop
- Verify SHA-256 before opening; do not disable Gatekeeper system-wide.
- App license session is separate from CLI login.
- Desktop does not run Skills — check the coding assistant if a workflow is missing.
Migrate