---
title: "Resources"
description: "CPU, memory, and disk — and how the agent scales them"
canonical_url: "https://hoplite.sh/docs/sandboxes/resources"
markdown_url: "https://hoplite.sh/docs/sandboxes/resources.md"
---

# Resources
URL: /docs/sandboxes/resources
LLM index: /llms.txt
Description: CPU, memory, and disk — and how the agent scales them
Related: /docs/sandboxes/previews

# Resources

Sandboxes start small and scale up when the workload needs it. The agent monitors its own environment — `sandbox_status` reports health, CPU, memory, and disk usage — and resizes when builds or dev servers demand more.

## Limits

On the default platform policy a sandbox can grow up to:

| Resource | Ceiling |
| --- | --- |
| CPU | 8 vCPU |
| Memory | 16 GiB |
| Disk | 10 GiB |

Limits are policy-layered — platform, plan, workspace, user, and thread levels can each tighten (never loosen) the bounds above them, so your effective ceilings may be lower.

## How resizing behaves

- **Scaling up** (`sandbox_resize_up`) is usually automatic. Policies can set approval thresholds, so a large jump may pause for your sign-off even below the ceiling.
- **How a change is applied depends on the active provider.** A provider can update a resource live, restart the runtime, or reject an unsupported axis. Hoplite reports the mode and never assumes that running background processes survived a disruptive change.
- **Scaling down** (`sandbox_resize_down`) covers CPU and memory only and requires your approval because the provider may restart the runtime.

## Running out of space

Daytona compatibility workspaces automatically grow their disk by 50% when they
report `ENOSPC`, rounded up and capped at the effective disk ceiling. Setup then
retries once because dependency installation is safe to repeat; other failed
commands are never replayed automatically, so the agent can inspect the
preserved failure and retry deliberately after the sandbox restarts. Modal, the
default provider for new workspaces, has fixed resource allocations, so the
agent reports an unsupported resize request instead of claiming a change was
applied.

## Sitemap

See the full [sitemap](/docs/sitemap.md) for all pages.
Well-known sitemap: [/docs/.well-known/sitemap.md](/docs/.well-known/sitemap.md).