# Sandboxes

A Sandbox supplies compute for Project development: running commands, preparing dependencies, and serving a working preview. It supports the editing process while a Site remains the separately managed production destination.

## Start with a working preview

Open the Project’s **Sandbox** view. If the environment is stopped, choose **Actions → Start**. Ask the Project to serve a page containing “Preview check”, then choose **Open preview** in **Sandbox**. In the **Browser** view, check that the page shows “Preview check”. Change it to “Preview updated” and reload. If the first version persists, inspect the development server output in **Terminal**. To put the page at a visitor-facing address, follow [Release a first Site](/docs/sites/quickstart).

## Work in development

Use the Project's working environment to make a change, run the relevant checks, and inspect the application preview. Confirm the preview reflects the code you intend to evaluate before releasing it.

- Project source and working files describe what you are developing.
- Development configuration supplies the authorized resources for that work.
- The Sandbox runs the commands and processes needed for development.
- A Site runs an explicitly selected production release.

## Diagnose an unavailable preview

Start with Sandbox state, then inspect process output in [Logs](/docs/services/logs). A stopped environment, failed dependency installation, application startup error, and application authorization failure require different responses.

| Symptom | Check |
| --- | --- |
| No preview is available | Environment and application startup state |
| The application fails to start | Dependency, build, and process output |
| The page opens but a feature fails | Application errors and development service configuration |
| Production behaves differently | The Site's release, credentials, and data |

Restarting compute is not a substitute for fixing an application error. Preserve the evidence needed to understand a failure before repeating the operation.

## Understand persistence and cost

Compute allocation and retained data have different lifecycles. A stopped runtime does not imply that its retained storage is free or deleted. Sandbox execution follows its own lifecycle and accounting; production VM lifecycle choices are separate.

Chats and Agents can use bounded execution for tasks without becoming Project development environments. A durable File system alone does not supply a persistent application backend. See [Runtimes](/docs/sites/runtime) and [File system](/docs/services/file-system).

## Example: inspect a new form

After adding a form to a Project, use its working preview to submit valid and incomplete inputs. If the preview is unavailable, inspect the development process output before repeatedly restarting the Sandbox.

Check the source revision being served and the configured development services. Continue with [Project development](/docs/projects/development), then [Testing](/docs/services/testing) before release.

## Availability

Use this guide for Project development Sandboxes. For a Chat or Agent task, inspect the conversation's execution evidence and [working files](/docs/services/file-system) instead of looking for a Project Sandbox. For a production failure, begin with the affected [Site](/docs/sites/operations).