---
title: "Full Linux VMs for your agents"
description: "BoxCompute VM Sandboxes are now the default runtime for every account, giving agents a full Linux virtual machine rather than a shared-kernel gVisor container. Each disposable VM boots its own kernel and provides root access, outbound internet with public IPv4 and DNS, and a unified approximately 10 GiB filesystem covering / and /workspace, while preserving the existing create, execute, file-transfer, and delete API. The CLI or HTTP API can create a VM, and users can opt out with vmSandbox: false or disable networking with blockNetwork: true. VMs remain billable until explicitly deleted and currently use a fixed profile of 0.5 CPU, 1 GiB memory, and a minimal Ubuntu image. The beta does not include inbound ports, SSH, custom images, or volumes."
---

# Full Linux VMs for your agents

[Boxcompute](https://yomu.fyi/company/boxcompute) · boxy · Sep 17, 2026

**Type:** Announcement

## Summary

BoxCompute VM Sandboxes are now the default runtime for every account, giving agents a full Linux virtual machine rather than a shared-kernel gVisor container. Each disposable VM boots its own kernel and provides root access, outbound internet with public IPv4 and DNS, and a unified approximately 10 GiB filesystem covering / and /workspace, while preserving the existing create, execute, file-transfer, and delete API. The CLI or HTTP API can create a VM, and users can opt out with vmSandbox: false or disable networking with blockNetwork: true. VMs remain billable until explicitly deleted and currently use a fixed profile of 0.5 CPU, 1 GiB memory, and a minimal Ubuntu image. The beta does not include inbound ports, SSH, custom images, or volumes.

## Context

The service began with gVisor, a fast sandbox that shares the host kernel. VM Sandboxes are now the default because their own guest kernel supports integrations and tools that assume a full operating system.

## Approach / What changed

Use the existing sandbox API or CLI to create, execute commands in, transfer files to, check, and delete a VM Sandbox. VM behavior is controlled with vmSandbox, which defaults to true; setting it to false selects gVisor, while blockNetwork: true creates a VM without a network interface.

## Takeaways

- VM Sandboxes boot their own Linux kernel, allowing root access, apt-get package installation, native-module builds, and tools that assume a full operating system.
- A VM provides outbound internet, public IPv4 and DNS, plus one approximately 10 GiB root filesystem shared by / and /workspace; blockNetwork: true disables networking.
- VMs do not auto-expire and remain billable until deleted. The beta fixes the profile at 0.5 CPU, 1 GiB memory, and a minimal Ubuntu image, without SSH, inbound ports, custom images, or volumes.

## FAQ

### How can an account opt out of VM Sandboxes?

Set vmSandbox: false when creating a sandbox to use gVisor instead. Omitting vmSandbox or setting it to true selects a VM.

### What happens if a VM is no longer needed?

VM Sandboxes do not auto-expire and remain billable until explicitly deleted. The CLI and existing API include a delete operation for cleanup.

### Can a VM be created without internet access?

Yes. Pass blockNetwork: true to create a no-NIC VM; otherwise outbound internet, public IPv4, and DNS are available by default.

**Tags:** [Linux](https://yomu.fyi/topic/linux), [Sandboxing](https://yomu.fyi/topic/sandboxing)

- Source: [Boxcompute](https://boxcompute.ai/blog/vm-sandboxes)
- Source URL: https://boxcompute.ai/blog/vm-sandboxes
- Ingested by Yomu: 2026-09-18T03:34:58.957Z

[Read original post](https://boxcompute.ai/blog/vm-sandboxes)