Rigs, easier setup, and more reliable connections
Rigs have a consistent name across Amika, agent setup takes fewer steps, and SSH and browser terminal sessions recover more smoothly from interruptions.
Overview
Sandboxes are now called rigs across the web app, CLI, and TypeScript SDK. Existing sandbox commands and links still work, so you can adopt the new names at your own pace. Rigs also connect more reliably through SSH and the browser terminal, and new users can get an agent running with fewer setup steps.
What's new
Rigs and the CLI
- Use rig names throughout Amika. Run
amika rigand use flags such as--rigand--rig-name. Existing sandbox commands and flags still work, and old sandbox links open the corresponding rig pages. - Start from the branch you're working on.
amika senduses your checked-out branch, and--new-branchbranches from it instead of the repository default. - Work in remote rigs. The CLI now creates remote rigs; local Docker rigs and their dedicated commands and flags have been removed.
- Use rig-named SDK methods and types to manage rigs, services, and snapshots. Existing sandbox-named SDK methods and types remain available as deprecated aliases.
Connections
- Open a rig from an editor link on the first try, even if you have not connected to it through the CLI before. SSH also recovers when saved connection details become stale.
- Connect from one rig to another with an isolated Amika SSH key, without forwarding unrelated keys from your computer.
- Return to your browser terminal after a brief interruption without starting a new shell. Expanding or closing the terminal also keeps your selected desktop tab in place.
- Open a rig in VS Code Desktop from its page in the web app.
Setup and everyday use
- Set up coding agents in fewer steps. Import credentials from each agent's CLI or enter an API key in the browser. New users can make commits in a rig without first setting a Git author name; a preferred name can still be set in Settings.
- Choose an integration before connecting its credentials. It becomes available to the rig after you connect them.
- Keep your preferred rig settings. New rigs use your repository's preset, size, and snapshot settings unless you choose different values.
- Find rig details and services more easily. Rig pages have a dedicated Information tab, and service lists show the services you created without system services mixed in.