Support

Support should be as direct as the product.

The fastest way to unblock KCC is to keep setup, machine readiness, and product support connected instead of splitting them across disconnected threads.

Getting started

Use guided onboarding when you want help connecting machines, repos, and account settings correctly from day one.

Technical support

Use the support contact for machine-specific issues so environment, auth, and control-plane state can be diagnosed together.

Release support

Package-channel installs should always map back to the same GitHub release and the same README/setup docs.

Contact

Need help with onboarding or enterprise planning?

Use the support or enterprise contact path so product, packaging, and control-plane questions stay in one place.

Recommended issue context

  • OS, terminal backend, and package channel
  • `kcc doctor` output or the failing command path
  • Whether the issue is local runtime, control plane, or chat gateway