Commands and processes

Run commands in an interactive remote shell, or send a command directly from your local terminal. Commands execute in the sandbox's repository directory and use its installed tools and environment.

Run a command from your computer

Local:

cube connect feature/payments --command 'git status --short'

connect selects an existing Session, resumes it if paused, and waits for readiness. The command's output appears in your local terminal, and its exit code passes through the CLI.

Quote the remote command so your local shell does not expand its variables or operators. For example, in a Bun repository:

cube connect feature/payments --command 'bun install && bun test'

An explicit --command is not automatically replayed after a connection loss. Inspect the result before deciding whether to run it again.

Run an interactive process

Open a shell and use the repository normally:

cube connect feature/payments

For a command that needs a terminal, add --tty:

cube connect feature/payments --tty --command codex

Configure the agent first. Use a persistent named terminal for an agent or service you want to detach from and revisit.

Keep a service running

Local: create a named remote terminal:

cube connect feature/payments --tmux web

Sandbox: start your project's development server. For a Bun project with a dev script:

bun run dev

Detach with Ctrl+B, then D. The process keeps running while the VM runs. Reconnect with the same --tmux web command to see output or stop the process with Ctrl+C. Different tmux names give you separate terminals in the same VM.

Use networking and tunnels to open the application locally. For container services, see Run Docker.

Process lifetime

A local disconnect and a VM pause have different effects. Persistent terminals survive a disconnect while the VM keeps running. Pausing the Session stops its processes; after resume, restart your agents, servers, and tests as needed.

See SSH and terminals for interactive connection recovery and Lifecycle for disk persistence.