Skip to main content
The connect command attaches an interactive terminal, a remote shell, to a running sandbox. It opens a real shell inside the sandbox over a PTY and streams keystrokes in and the shell output back. Run commands, inspect state and debug as if sitting at the sandbox’s own terminal.
The sandbox must already be running. connect attaches to an existing sandbox by its ID and does not create one. Disconnecting leaves the sandbox and other sessions untouched.
Install the CLI and set the PPIO_API_KEY and PPIO_DOMAIN environment variables before running these commands. See Install and authenticate.

Usage

The command also has short aliases, sbx for sandbox and cn for connect, so ppio sbx cn <sandbox-id> connects as well.

Arguments

string
required
ID of the running sandbox to connect to.

Options

boolean
Secures sandbox controller traffic. --no-secure disables it.
boolean
Allows sandbox URLs without a traffic access token. Alias: --allow-public-traffic.
boolean
Requires a traffic access token for sandbox URLs and prints the token. Alias: --no-allow-public-traffic.
string
Output format: pretty, json or yaml. Legacy aliases: -f, --format and --json.
string
Sandbox lifecycle timeout after connect.
boolean
Returns connection details without opening a terminal.

Connect to a sandbox

On connect, the CLI prints the sandbox’s dashboard inspect URL and a confirmation line, then hands the terminal over to the sandbox shell:
Output

End the session

Exit the shell as usual, with exit or Ctrl+C. The CLI cleans up the terminal, closes the connection and prints:
Output
Disconnecting only ends the terminal session. It does not stop or kill the sandbox, and it does not disconnect other users connected to the same sandbox.
Last modified on November 19, 2026