Operator CLI

polychrome-cli ships a polychrome binary that targets whichever kubectl context is selected — no --context flag. Pick one with kubectl config use-context.

Commands

polychrome up                      # apply manifests/overlays/<auto-detected>
polychrome status                  # pod readiness + AgentService health + Leases
polychrome ps                      # compact pod listing
polychrome logs control-plane -f   # tail control-plane logs
polychrome exec <pod> -- /bin/sh   # debug shell into a pod
polychrome send <conv-id> "hello"  # drive AgentService.Connect end-to-end
                                   #   (opens a port-forward; no manual kubectl)
polychrome restart --wait          # down + up, block until Ready
polychrome down                    # delete the overlay
polychrome upgrade                 # self-update from GitHub Releases

Overlay auto-detection

up / down / restart auto-detect the overlay from the context name — orbstack, kind-*, and minikube map to local; anything else maps to gke. Override with --overlay {local,gke} or --overlay-path <PATH>.