Setup bootstrap

Honest bootstrap for missing Helm / Argo / Prometheus — dry-run by default, approve-gated apply. What kprompt setup installs and what it never does.

kprompt setup turns tools.Detect gaps into a reviewable plan. Default is dry-run. Host and cluster installs need --approve or interactive confirm — never silent. Full flag reference lives in the product docs on GitHub.

kprompt tools
kprompt setup
kprompt setup --profile minimal --approve
kprompt setup --profile platform --only prometheus --approve

Profiles

Profile	Components	Notes
minimal	Helm	Host lane only
platform (default)	Helm + Argo Workflows + Prometheus stack	Approve-gated cluster installs
full	platform + Grafana + OTel URL steps	Config lane is hints only — never auto-writes ~/.kprompt/config

What setup installs (with --approve)

Helm CLI on PATH via Homebrew or get-helm-3 (OS matrix in product docs)
Argo Workflows controller manifests into namespace argo (pinned release YAML)
kube-prometheus-stack via Helm into namespace monitoring (release kprompt-prom)

What setup does not do

Does not create clusters (kind / minikube / EKS / GKE provisioners)
Does not install Tekton, KEDA, Istio, Linkerd, Crossplane, Flux, or Argo CD
Does not replace Helmfile, Terraform, or Crossplane as a general installer
Does not auto-write Grafana / OpenTelemetry URLs (print config set hints only)
Does not wipe or uninstall — wipe-class helm uninstall / namespace delete stay hard-denied
Does not run in the background or install while you optimize

Missing-tool hints

When kprompt tools or a prompt path finds Helm, Argo Workflows, or Prometheus missing, hints point at kprompt setup with the right --profile / --only. Prefer pointing at an existing Prometheus URL when you already have one.

Safety model is unchanged: cluster installs are plan → safety → approve → apply, same as any other mutate. Already have Prometheus / Grafana / OTel? Prefer bind-over-install — see Adopt (15 min).