**After installation, point the app at a kubeconfig that can reach a running cluster (KUBECONFIG or ~/.kube/config).**
**Download CLI installs gcloud, az, aws, oci, doctl, ibmcloud, or kubelogin into the app so the sandbox can start them and refresh a token. A CLI installed on the host still cannot be started. A certificate or token in the kubeconfig needs no CLI. 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).
The mouse pointer is hidden while the bubbles screen saver is showing.
Full screen with F11. Optional idle bubbles screen saver while full screen.
Catalog can collapse to a Connections rail. Overview charts load sooner. Flatpak installs kubelogin with Download CLI.
S3 Browser and Longhorn backup actions. Cloud adds Google, Azure, Amazon, Oracle, DigitalOcean, or IBM.
About, What's New, logs, and crash reports use the shared desktop windows.
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.