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

Prerequisites

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

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.

Copy files

Use amika scp to copy files between your machine and a rig. It uses the same SSH identity as amika rig ssh and accepts standard scp options such as -r, -p, and -C.
A relative rig path starts under /home/amika. Use an absolute path when the file lives elsewhere in the rig.

Local-Docker shell (CLI only)

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

Open in an editor (CLI only)

amika rig code opens the rig in Cursor, VS Code, Claude Desktop, or Codex over SSH. See Open a rig in your editor for the full command and instructions for other Remote-SSH editors.

Revoke an SSH token

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

Next steps

Programmatic walkthrough

Rig lifecycle

CLI reference