Runtime and tools

An Adria sandbox is a Linux VM with its own filesystem and processes. The standard Session image provides a development environment for your repository, agents, and services. The shell opens in /home/cube/workspace/<repo> as the cube user.

Included tools

Agent packages are installed without customer credentials. Connect your agents before launching them. Interactive desktop capabilities require an image with computer-use support.

Install project dependencies

Use your repository's usual setup commands inside the sandbox. For a Bun project, for example:

bun install
bun run build

Installed dependencies and files stay on the Session disk across disconnects and pauses. Save your environment files once to reuse them in new and resumed computers. Other local files and shell variables are not automatically copied.

Run services

The cube user can run Docker and use sudo inside the VM. Start databases and other dependencies using your project's setup, or follow Run Docker. Agents with this access can modify the sandbox's files and services.

Separate sandboxes can use different dependency versions and the same service ports. Terminals connected to one Session share its filesystem and processes. Use local tunnels to reach a service from your computer.

Keep your setup

Adria prepares the repository and your saved setup before opening the shell.

Updating your local CLI does not replace an existing Session's image or disk. A paused Session resumes with its existing files; you must restart its services and agents. Deleting the Session permanently removes those files. See Lifecycle.