Skip to main content
A rig is an isolated devbox: a sandboxed VM tuned for coding agents. Agents and people can work in the same repository and environment on it, without touching each other’s work or your everyday machine. Each rig includes:
  • One or more agent harnesses, such as Claude Code, Codex, OpenCode, or Pi
  • Your Git repositories, dependencies, tools, and development services
  • Agent credentials, environment variables, and secrets your agent can never read
  • SSH access and URLs for exposed services
  • VM snapshots to save a rig’s filesystem and then boot new VMs from it
Amika provisions the VM, prepares it from your repository configuration, and connects it to the control plane. You can then operate the rig and its agents from the web UI, CLI, TypeScript SDK, HTTP API, chat integrations, or your editor.

​
Shared by agents and people

You can give an agent a rig and let it work in the background, or you can use the rig interactively, just like a normal cloud devbox. You, your teammates, and your agents can connect to a rig at any time to inspect files, run commands, write code, open your repo in an editor, and view dev server URLs. A single rig can run multiple agents at the same time (it’s just a VM!). All rigs are on a mesh network, so rigs and your agents can communicate with other rigs when work needs to span environments.

​
Persistent or temporary

Choose the lifetime that fits the task:
  • Temporary rigs start clean for a branch, pull request, check, or one-off task. Delete them when the work is complete.
  • Persistent rigs keep their filesystem and environment available for an ongoing project or durable automation. Stop them when idle and start them again later.
You can capture a configured rig as a snapshot to create more rigs from the same starting point.

​
Where rigs run

Rigs can run on computers you already own, such as a Mac Mini, a desktop, an EC2 in your VPC, or a sandbox cloud account you already have. Install the Amika host daemon on a machine and it can run several isolated rigs side by side. See Bring your own compute. If you’d rather not run hardware, Amika hosts rigs too. A rig runs on Amika’s hosted compute unless you pick one of your hosts when you create it.

​
Next steps

Create a rig

Provision a rig with your repository and agent credentials.

Rig lifecycle

List, stop, start, and delete rigs.

Connect to a rig

Open a shell or connect with an editor.

Bring your own compute

Run rigs on your own machines instead of Amika Cloud.

Configure a repository

Define reproducible rig settings alongside your code.