Try Kubius
⌘K

Observability

Terminal

Open an interactive shell into any running container without leaving Kubius.

How to open

There are three ways to open a terminal:

  • Pod detail → Actions menu → Terminal
  • Right-click a Pod row → Open Terminal (in any list that shows pods - Pod list, Node Pods tab, Deployment Pods section, related-resources panels)
  • Pod list toolbar → Open Terminal when a single pod is selected

Pods that aren’t in the Running state get the menu item greyed out - exec only works on running containers.

What you get

The terminal is a full xterm-compatible emulator (powered by SwiftTerm):

  • 256-colour support
  • Mouse selection, copy / paste (⌘C / ⌘V)
  • Resize when you resize the window
  • TERM is set to xterm-256color

It connects via the K8s /exec SPDY/WebSocket endpoint with a TTY allocated, so editors like vim/nano, interactive REPLs (python, node), and htop all work correctly.

Container selection

If the pod has multiple containers, Kubius picks the first one by default. To use a different one, open the terminal via the Pod detail Actions menu after switching containers in the container picker (visible in the Overview tab’s container section or the Logs tab).

Default shell

Kubius tries shells in this order: /bin/bash, /bin/sh, sh. If none are present in the container (e.g. distroless images) the connection fails - that’s a limitation of kubectl exec too, not specific to Kubius.

Clean exit

When you exit the shell the window closes automatically. If the exit code was non-zero (broken pipe, container died), the window stays open with the error.

Window lifecycle

Terminal windows are tracked per pod. Opening a terminal for the same pod that already has one brings the existing window to front. Switching cluster closes every open terminal window - they belong to the cluster they were spawned against.