Sandboxes

Start with a purpose

A sandbox is useful for a build, a test, a coding agent or a short-lived development environment. Choose its template, workspace and resource size for the workload you intend to run.

Understand the lifecycle

The local lab uses four visible actions: create, pause, resume and remove. Pausing keeps the simulated machine available to resume. Removing it ends that instance. A saved snapshot is a separate recovery point.

Action	What to check
Create	The returned identifier and initial state
Execute	Exit status, stdout and stderr
Pause	Whether work is still running and what state is retained
Snapshot	The saved version and its resource scope
Remove	Whether required data was stored elsewhere

Inspect readiness

“Running” does not necessarily mean an application is ready to serve requests. Check the process, the listening port, and an application-level response. Use the platform’s readiness contract where one is available.

Try the local sandbox API

The API explorer can create and list example resources in a process-local store. It is intentionally isolated from real cloud infrastructure. Restarting the app clears these API examples.

Practice

Open Your first sandbox to try the lifecycle visually, then read snapshots and persistence.