Skip to main content
A running sandbox is reachable over SSH, so you can attach any IDE or ADE (agentic development environment) that supports remote SSH — Cursor, VS Code, and their forks — and edit the sandbox’s files as if they were local.

​
Prerequisites

  • A remote sandbox in the active / running / started state. See Create a sandbox.
  • An editor with a remote-SSH extension (for example Remote - SSH in Cursor or VS Code).

​
Cursor

Use the CLI to open the sandbox directly:
This registers the managed SSH alias and launches Cursor against it. See Open a sandbox in your editor for details and troubleshooting.

​
VS Code and other Remote-SSH editors

Any editor that reads your ~/.ssh/config can connect to a sandbox through the Amika-managed SSH host alias.
  1. Run amika sandbox code dev-box once. This writes the alias amika-<sandbox-id> into ~/.ssh/amika.conf and ensures your ~/.ssh/config includes that file.
  2. In your editor, open the remote-SSH host picker and choose the amika-<sandbox-id> host.
  3. Open the repository folder inside the sandbox (typically under /home/amika/workspace).
Alternatively, get the raw SSH destination and hand it to your editor or SSH client directly:
SSH connection tokens are time-bounded and rotate. The managed alias tracks the current details, so re-running amika sandbox code refreshes it if a connection stops working. See SSH and connect for the full SSH surface, including revoking a token.

​
Browser access

To drive an agent from the browser instead of a local editor, use the OpenCode web console. See OpenCode for managing its access credentials.

​
Next steps

Open a sandbox in your editor

SSH and connect

OpenCode