Skip to main content
Once a sandbox is running, you have a few ways to get inside it:
  • SSH (works on hosted sandboxes) — for interactive shells, one-off commands, or for handing the destination to your own SSH client.
  • sandbox connect (CLI-only, local sandboxes) — drops you into the Docker container’s shell directly.
  • sandbox code (CLI-only) — opens the sandbox in Cursor over SSH.

Prerequisites

A sandbox in the active / running / started state. See Create a sandbox.

Open an interactive SSH session

Run a one-off command

The CLI passes anything after -- straight to the remote shell. Use -t to allocate a TTY when the remote command needs one.

Local-Docker shell (CLI only)

amika sandbox connect opens the Docker container’s shell directly. It only applies to local sandboxes (--local).

Open in Cursor (CLI only)

amika sandbox code opens the sandbox in Cursor over SSH.

Revoke an SSH token

The SSH credential issued by ssh/getSSH is time-bounded. You can revoke it on demand.

Next steps

Programmatic walkthrough

Sandbox lifecycle

CLI reference