Frequently asked questions

Is a sandbox a container?

An Adria sandbox is a Linux VM with its own filesystem and processes. You can run Docker containers inside it.

Is a Session different from a sandbox?

Session is the name used by the CLI for your sandbox. It associates the computer with a repository and branch.

Can I use my own coding agent?

Yes. The standard image includes Codex, Claude Code, and Pi. Connect your credentials, then launch the agent inside the sandbox.

Does Adria include a built-in agent?

The dashboard supports Adria workflows. The current workflow reviews merged pull requests and proposes architecture documentation updates in Notion, with approval for each page proposal.

What survives a pause?

Files on the Session disk survive. Running processes, RAM, tmux terminals, agent processes, and browser tabs do not. Restart them after resuming.

Are local files copied when I start?

The repository is checked out from GitHub. Local uncommitted changes, unpushed commits, and ignored files are not copied automatically. Push commits first, or transfer files explicitly. For .env files, use cube env import to save them once for new and resumed computers.

Can two sandboxes use the same port?

Yes. Each has an independent network environment. Use separate local ports when forwarding both to your computer.

Does closing a terminal stop billing?

No. The VM keeps running until paused or deleted. Running VMs use compute credits. Inspect them with cube sessions and check usage and credits.

Are agent model costs included?

No. Your subscription includes Adria compute credits. Coding-agent subscriptions and model usage are billed separately by your provider.

Can I recover a deleted sandbox?

Deleting a Session permanently removes its disk. Push commits and copy any files you need before using cube kill.

Where should I start if something fails?

See troubleshooting for authentication, startup, configuration, previews, and desktop issues.