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

# Sandboxes

> Monitor and manage the sandboxes where the AI runs code

A sandbox is an isolated environment where the AI can run code for a user, for example to analyze data or to make a file. The **Sandboxes** screen shows the sandboxes of your users and the state of the sandbox service.

Open the **Admin** group in the sidebar and click **Sandboxes**. Only admins see this screen.

## The Sandbox Access permission

The **Sandbox Access** permission controls if the AI can run code in a sandbox for a user. An admin always has this access.

The permission is on by default for a user account. The **Invite User** page starts with it off, so turn it on when you invite a user who needs it. To change it later, open the user in **People** and find the **Sandbox** group in **Permissions**. See [Roles & Permissions](https://docs.relayhub.ai/administration/user-management/permissions.md).

## Totals

Four figures show at the top of the screen:

* **Total Sandboxes**: the number of user sandboxes
* **Active Now**: the number of sandboxes in use now
* **Disk Usage**: the disk space that all sandboxes use
* **Commands Today**: the number of commands that ran today

Click the **Refresh** icon to load the newest figures.

## Skill sandbox runtime

Skill runs use short-lived sandboxes. These are separate from the user sandboxes in the table. The **Skill sandbox runtime** section shows:

* **In use**: the number of slots in use, out of the maximum
* **Runtime**: the type of runtime that the service uses
* **Cleaned up**: the number of abandoned sandboxes that the service removed
* **Last check**: the time since the last cleanup check

The section shows a message when there is a problem:

* "The sandbox controller is not reachable." Skills that need a sandbox fail.
* "The cleanup task has stopped running." Abandoned sandboxes keep their slots until the service restarts.
* "Every sandbox slot is in use." New skill runs fail until a slot is free.

If one of these messages stays, contact your RelayHub support contact.

## User sandboxes

The table shows one row for each user sandbox, with the **User**, **State**, **Disk**, and **Last Activity**. The state is one of **RUNNING**, **IDLE**, **STOPPED**, **CREATING**, or **READY**.

Click the user name to open the **Command History** of that sandbox. The history shows each command, its exit code, its duration, and the start of its output. A **BLOCKED** label shows a command that RelayHub stopped, with the reason.

## Stop or reset a sandbox

> [!WARNING]
>
> A reset removes all the packages and files in the sandbox. You cannot undo it.

Use the icons in the **Actions** column:

* **Stop**: stops a sandbox in the **RUNNING** or **IDLE** state.
* **Reset to base image**: returns the sandbox to its first state. Confirm the message to start the reset.


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