**After installation, point the app at a kubeconfig that can reach a running cluster (KUBECONFIG or ~/.kube/config).**
**A login that starts a program on this computer, such as aws, gcloud, or kubelogin, cannot start that program from the sandbox. A certificate or token in the kubeconfig is enough. Localhost on this computer stays reachable, including a local cluster API, local Ollama, and a port-forward opened in the browser.**
Browse a Kubernetes cluster from the desktop using your kubeconfig. Apply YAML, follow logs, exec into pods, and manage port-forwards without a browser.
Settings stay on this computer. Cluster access uses the network and files under the home folder (typically ~/.kube).
A ControllerRevision opens in the details pane. Its data values are shown as text.
Chat on the cluster overview when AI is on. The details pane can collapse to a rail.
A drain note when AI is on. Cordon and Drain stay hidden unless another Ready node remains.
Helm release history, a drain preview table, and What's New. The catalog radio sets kubectl current-context only.
Source folders follow the client and UI areas. Flathub and Store submission notes are in packaging.
Pod terminal, workload rollouts, storage and access actions, and YAML highlighting.