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

# Manage sandboxes in the PPIO console

> Use the AGENT SANDBOX pages of the PPIO console to inspect running sandboxes, browse templates, track usage and quotas, and save a sandbox as a snapshot.

The [PPIO console](https://console.ppio.ai) is the web interface for Agent Sandbox. It lists the sandboxes, templates and snapshots of a team, shows usage and quotas, and creates a sandbox without the SDK or the CLI. This page describes the sections and the two flows that the console covers on its own.

## AGENT SANDBOX pages

> [card] [AGENT SANDBOX › Sandboxes](https://console.ppio.ai/sandbox)
>
> Search running sandboxes by ID and filter by creation time, template, vCPU and memory.

> [card] [AGENT SANDBOX › Templates](https://console.ppio.ai/sandbox/templates)
>
> Public PPIO templates and the team's own, searched by ID, visibility, vCPU and memory.

> [card] [AGENT SANDBOX › Snapshots](https://console.ppio.ai/sandbox/snapshots)
>
> Lists saved snapshots that new sandboxes can start from.

> [card] [AGENT SANDBOX › Playground](#create-a-sandbox-from-the-playground)
>
> Creates a sandbox in the browser.

> [card] [AGENT SANDBOX › Usage](#usage)
>
> Shows the daily resource usage and cost of the team.

> [card] [AGENT SANDBOX › Quotas & Limits](https://docs.ppio.ai/sandbox/quotas.md)
>
> Shows the team's quota values and the form for a higher limit.

The sandbox list searches by sandbox ID and filters by creation time, template, vCPU, memory and other attributes. The template list holds public templates provided by PPIO and the team's own [custom templates](https://docs.ppio.ai/sandbox/templates/build.md); search by template ID, and filter by visibility (public, private or all), vCPU and memory.

## Sandbox list actions

The **AGENT SANDBOX › Sandboxes** page reloads with **Refresh**, and **Create sandbox** opens the Playground. Each row of the list has these actions:

> [card] Connect
>
> Offers **Open web terminal** and **Copy CLI command** for reaching the sandbox.

> [card] Save as snapshot
>
> Saves the current state of the sandbox as a snapshot.

> [card] Extend timeout
>
> Adds time to the remaining lifetime of the sandbox.

> [card] Pause
>
> Suspends the sandbox and keeps its state.

> [card] Resume
>
> Brings a paused sandbox back to Running.

> [card] Kill
>
> Terminates the sandbox.

> [card] Open details
>
> Opens the sandbox page, with the tabs **Overview**, **Metrics**, **Logs**, **Terminal** and **Events**.

> [card] Copy Sandbox ID
>
> Copies the sandbox ID.

## Create a sandbox from the Playground

**1. Open the Playground**

Go to **AGENT SANDBOX › Playground** in the console.

**2. Choose a region**

Select the **Region**. The **Source** list changes with the region.

**3. Choose a source**

Select the **Source**: a template or a snapshot.

**4. Set the lifecycle**

Under **Lifecycle**, choose **Long running** or **Custom**.

**5. Set the timeout behavior**

Under **On timeout**, choose **Pause** or **Kill**. To resume the sandbox when a request arrives after a pause, enable **Auto-resume**. The option appears only when **On timeout** is **Pause**.

**6. Add metadata**

Add entries under **Metadata (Optional)** if the sandbox needs them. Metadata is fixed after creation.

**7. Create the sandbox**

Select **Create sandbox**.

## Save a sandbox as a snapshot

**1. Open the sandbox list**

Go to **AGENT SANDBOX › Sandboxes**.

**2. Start the snapshot**

In the row of a running sandbox, open the actions and select **Save as snapshot**.

**3. Save the snapshot**

Optionally enter a name, then save the snapshot.
\[!WARNING] The name is permanent and cannot be changed after the snapshot is created.
For what a snapshot contains, see [Save and restore sandbox state with snapshots](https://docs.ppio.ai/sandbox/snapshots.md#what-a-snapshot-contains).

## Usage

**AGENT SANDBOX › Usage** shows three daily figures for the team.

| Figure | What it shows |
| - | - |
| vCPU hours | Total vCPU runtime across all sandboxes for the current day, in hours, calculated with second-level precision. |
| Memory hours | Total memory usage across all sandboxes for the current day, in GiB-hours, calculated from the allocated memory and the runtime of each sandbox. |
| Usage costs | Total resource cost for the current day, including vCPU and memory costs. The billing rules are in [How Agent Sandbox billing works](https://docs.ppio.ai/sandbox/billing.md). |

All resources are billed by the second and displayed at daily granularity. A chart shows the usage trend.

> [!NOTE]
>
> Usage data does not always include the most recent usage. It can differ slightly from the final bill. Final charges come from the bill in **Billing › Overview**.


## Related topics

- [Save and restore sandbox state with snapshots](https://docs.ppio.ai/sandbox/snapshots.md)
- [What is a sandbox template?](https://docs.ppio.ai/sandbox/templates/overview.md)
- [Install and sign in to the PPIO CLI](https://docs.ppio.ai/sandbox/cli/install.md)


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