Troubleshooting

Use this page when a command fails during setup. Start from the symptom closest to your error output.

Symptom: harness.json not found

• Cause: you ran a command that expects an initialized harness before running harness-kit init.
• Fix: initialize first, then retry.

Symptom: Unknown category in list command

• Cause: using docs grouping names (workflow, stack, techstack) with CLI --category.
• Fix: use valid CLI categories.

Symptom: command not found (harness-kit)

• Cause: CLI is not globally installed or global bin path is not available in your shell.
• Fix: use npx directly, or install globally and restart shell.

Symptom: setup works but files seem incomplete

• Cause: expected bundles were not selected in the wizard, or were not added yet.
• Fix: inspect installed bundles, then add missing ones explicitly.

Symptom: unsure if current state is healthy

• Fix: run status to audit drift and required files, then resolve reported issues.