Terminal integrations

Adria connects your local terminal to the sandbox over SSH. Multiple terminals on the same Session share the checkout, files, and running services.

Choose a local terminal

cube connect feature/payments --terminal current
cube connect feature/payments --terminal cmux
cube connect feature/payments --terminal tmux

The default is auto. Adria uses the available terminal integration, or the current terminal. Select current when you want the shell in the pane you are already using.

In cmux, the workspace is bound to the Session so additional splits can connect to the same computer. Use separate workspaces for separate sandboxes.

Keep a remote terminal running

A local tmux integration and a remote tmux session have different roles. --terminal tmux selects the local integration; --tmux names a terminal running inside the sandbox:

cube connect feature/payments --tmux agent

Run an agent or server in that terminal. Detach with Ctrl+B, then D, and reattach with the same command. The remote terminal keeps running while the VM runs.

Disconnect and reconnect

Interactive connections can reconnect after a temporary network interruption. A disconnected terminal does not pause the sandbox or stop compute usage.

Pause stops all processes, including tmux and agents. After resuming, your files remain, but you must restart those processes. See lifecycle.

Connect an editor

For editors that support OpenSSH configuration, generate a temporary config with cube connect <session> --ssh-config. Follow the SSH guide for its short-lived credentials and standard SSH access.