Skip to main content
Volumes are persistent, team-scoped filesystems that you can attach to a CPU sandbox at launch. You can attach a volume to multiple sandboxes, and a volume is synced across writes. A volume persists even after all sandboxes are stopped, so you can completely isolate your data needs from your sandbox compute. Shared volume mounts are not supported by GPU sandboxes or macOS sandboxes. GPU sandboxes use ephemeral disk; macOS sandboxes use persistent disks.

Quick Start

  1. Create a volume.
  2. Mount it when creating a sandbox.
  3. Read and write files at the mount path.

Why Volumes

Use volumes when you need data to outlive a sandbox and be reused later:
  • Persistent workspaces for agents.
  • Reusable caches across runs.
  • Shared read only data mounted into multiple sandboxes over time.

Volume Lifecycle

  • Create volumes via SDKs, volume endpoints, or hx vm volumes.
  • Mount volumes during sandbox creation
  • Access files through the mounted path with normal sandbox filesystem operations.
  • Delete unused volumes with client.volumes.delete, DELETE /api/volume/:key, or hx vm volumes delete. Active mounts and ambiguous names return 409.

In This Section