Computers and sandboxes
The machines agents work on: cloud sandboxes, desktops, SSH computers and local worktrees, with sizes, regions, billing and takeover.
On this page
Every run happens on a machine. It can be a worktree on your Mac, a disposable cloud sandbox, a desktop with a screen for browser or simulator work, or a computer you own reached over SSH. You add and manage machines in Settings → Computers & sandboxes, and watch them live in Fleet.
Kinds of machine
| Kind | What it is | Cost to you | Good for |
|---|---|---|---|
| Local worktree | A git worktree on your Mac, run by Paradev’s host-service | None from Duun | Fast iteration with your own tools |
| Cloud sandbox | Disposable Linux with cached deps. Standard or Large. | Billed per second while it runs | Parallel runs, isolation, Autonomous in sandbox |
| Desktop | A machine with a display agents may need: browser, simulator, IDE | Cloud desktop billed per second; This Mac is owned | UI checks, end-to-end tests, screenshots |
| SSH computer | A build box, staging server or GPU host. We generate the key. | Owned: no compute charge | Special hardware, private networks, big builds |
Local worktrees are covered in Runtimes. The rest of this page is about the machines you add in Settings.
Cloud sandboxes
Select Cloud sandbox to create one. A sandbox is ready in about 20 seconds and billing is per second while it runs.
| Size | CPU and memory | Typical use |
|---|---|---|
| Standard | 2 vCPU · 4 GB | Tests, linting |
| Large | 4 vCPU · 8 GB | Builds, end-to-end tests |
| XL | 8 vCPU · 16 GB | Monorepo builds |
Choose a Region (US East, EU West or Asia Pacific) close to the services your tests call, and what to Start from: a repo snapshot or Blank Ubuntu 24.04. Snapshots include node_modules and build caches, so first runs are fast. See Images and networking.
Factories create sandboxes for you when a run needs one. Each repo in a factory’s Repos tab has a sandbox size: Standard (“Most repos”) or Large (“Monorepos, heavy builds”).
Idle timeout
Sandbox idle timeout stops sandboxes that have had no activity for the chosen time. “Idle sandboxes stop and stop billing.” A stopped sandbox keeps its disk until the run ends, so a run that resumes after an approval picks up where it left off.
Desktops
Select Desktop for work that needs a screen. Pick a Display: Browser (Chromium) or IDE (VS Code). Two kinds are available:
- Cloud desktop: Ubuntu 24.04 with Xfce, in the region you choose, billed like a sandbox.
- This Mac: your own Mac, paired through the Paradev app. Owned, so no compute charge.
With Desktop approval on in Settings → Action approvals, Duun asks before an agent takes control of a desktop or browser.
SSH computers
Select SSH computer and enter the Host, User and Port. Duun generates a key pair for this machine and shows the public key: add it to ~/.ssh/authorized_keys for that user, then test the connection.
“Duun connects with its own key. Agents get a shell; you approve risky commands as usual.” The machine is marked owned: Duun doesn’t charge compute for it. Removing it revokes Duun’s key; the machine itself is untouched.
Shared computers
By default Any thread can use shared computers: any run or conversation can be scheduled on a machine you’ve shared with the workspace. Turn it off and only threads you point at a computer can use it.
Watching and taking over
Open a machine from Fleet or from a run’s Open the machine running this link to see its terminal mirrored live, or its screen for desktops. A headless machine has no display: the agent works through its terminal, mirrored live.
To step in, select Take over (or press T in Inbox). You get a read-write shell as yourself; the session is audited. The agent pauses until you choose Hand back to the agent, and the run transcript notes what you changed.
Screen recordings
With Keep screen recordings on, desktop sessions are recorded and stored as run artifacts, with the last 30 minutes kept per session. Choose how long to keep them; older recordings are deleted.
Isolation
The agent runs as an unprivileged user with a per-run config. On SSH computers its config is mounted per run, never in your home folder. Each run gets its own working directory and branch, so parallel runs on one machine don’t touch each other’s files. Secrets are mounted as environment variables for the run that needs them and removed when it ends.
Stopping and removing machines
From a machine’s menu:
- Stop halts a sandbox or desktop and stops billing. You can’t stop a machine while an agent is using it: the menu says which agent and run.
- Delete machine (cloud) deletes its disk, caches and recordings. This can’t be undone. The run’s transcript and artifacts are kept.
- Remove (SSH) revokes Duun’s key.
API
Machines appear in webhook events as machine.created. See Event catalog.
Related
- Images and networking
- Runtimes
- Permissions and approvals
- Tour of the app in the help center