> ## Documentation Index
> Fetch the complete documentation index at: https://celesto.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# celesto sandbox delete

> Use celesto sandbox delete to remove one sandbox or clean up every sandbox on the host with a confirmation step.

`celesto sandbox delete` removes sandboxes and releases their stored resources. Use it for normal cleanup after a workflow, or with `--all` when you want to clear every sandbox on the host.

## Synopsis

```bash theme={null}
celesto sandbox delete <sandbox...> [OPTIONS]
celesto sandbox delete --all [OPTIONS]
```

## Arguments

**sandbox...** `string`

One or more sandbox names or IDs to delete.

## Options

**--all** `flag`

Delete every sandbox on the host.

**--force** `flag`

Skip the confirmation prompt for `--all`. Required for `--all --json`.

**--dry-run** `flag`

Show what would be deleted without deleting anything.

**--json** `flag`

Print a JSON envelope instead of formatted text.

> [!WARNING]
>
> `celesto sandbox delete --all --force` deletes every sandbox on the host. Use `--dry-run` first when you are unsure.

## Examples

### Delete one sandbox

```bash theme={null}
celesto sandbox delete my-sandbox
```

### Delete several sandboxes

```bash theme={null}
celesto sandbox delete test-a test-b old-agent
```

### Preview full cleanup

```bash theme={null}
celesto sandbox delete --all --dry-run
```

### Delete every sandbox

```bash theme={null}
celesto sandbox delete --all --force
```

### Use JSON in automation

```bash theme={null}
celesto sandbox delete --all --force --json
```

## What gets cleaned up

For each target, Celesto stops the sandbox if needed, removes its runtime state, releases network resources, deletes the per-sandbox disk state it owns, and removes the sandbox's `<vm_id>.log` runtime log.

### Reclaiming a leaked disk

If a sandbox row has already been dropped from the inventory but its per-sandbox disk still exists on disk, `celesto sandbox delete <id>` reclaims the disk by deriving its path from the sandbox ID instead of failing with "not found". This covers cases where a crash or an interrupted teardown left a disk behind without a matching row.

To sweep leftovers from sandboxes whose IDs you no longer know, use [`celesto sandbox prune`](https://celesto.ai/docs/celesto/cli/sandbox-prune).

## Related commands

* [`celesto sandbox list`](https://celesto.ai/docs/celesto/cli/list) - Review targets before deleting
* [`celesto sandbox stop`](https://celesto.ai/docs/celesto/cli/stop) - Stop without deleting
* [`celesto sandbox prune`](https://celesto.ai/docs/celesto/cli/sandbox-prune) - Sweep disks and logs left behind by deleted sandboxes
* [`celesto prune`](https://celesto.ai/docs/celesto/cli/prune) - Remove old image caches


## Related topics

- [celesto sandbox list](https://celesto.ai/docs/celesto/cli/list.md)
- [celesto sandbox stop](https://celesto.ai/docs/celesto/cli/stop.md)
- [celesto sandbox create](https://celesto.ai/docs/celesto/cli/create.md)
- [celesto sandbox prune](https://celesto.ai/docs/celesto/cli/sandbox-prune.md)
- [celesto doctor](https://celesto.ai/docs/celesto/cli/doctor.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.