> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/runners/what-are-runners.md).

# What Are Cloud Sandboxes?

A cloud sandbox is the environment that does the work when you start a run on the default execution target. TestVibe allocates an isolated sandbox for that run, prepares it automatically, executes your Playwright tests inside it, and tears it down afterwards.

You never install, register, or maintain anything — sandboxes are built for running AI-generated code safely, and each run gets its own.

## What A Sandbox Does

| Step                    | What happens                                                                                                              |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Load your project       | The sandbox receives the selected tests and configurations from your project.                                             |
| Prepare the environment | Browsers and test dependencies are set up automatically.                                                                  |
| Run browser tests       | Playwright opens your target site and follows the test steps.                                                             |
| Stream live status      | Per-scenario and per-step status streams into the app while the run executes.                                             |
| Upload evidence         | Screenshots, videos, traces, console logs, and network details upload to TestVibe's cloud and appear in the Runs section. |

## Run Lifecycle

| State                               | Meaning                                                         |
| ----------------------------------- | --------------------------------------------------------------- |
| Queued                              | The run is waiting for a sandbox.                               |
| Preparing                           | A sandbox is being allocated and set up.                        |
| Running                             | Tests are executing; live status streams into the app.          |
| Passed / Failed / Cancelled / Error | The run reached a terminal state and its evidence is available. |

For how this looks in the app, see [Understand live run status](/run-tests/understand-live-run-status.md).

## Reaching Your Site

The cloud sandbox opens your site URL from TestVibe's cloud. Public and staging URLs work without any setup. If the application is private or internal, you have two options that don't change anything else about the run:

* Reach it through a [tunnel device](/account-settings/tunnel-devices.md) so the sandbox can dial inside your network, or
* Run the tests on a [private runner](/runners/self-hosted-runners.md) you host inside your firewall instead.

See [Choose an execution target](/runners/choose-a-runner.md) to decide which fits.

## Related Help

* [Choose an execution target](/runners/choose-a-runner.md)
* [Private runners](/runners/self-hosted-runners.md)
* [Understand live run status](/run-tests/understand-live-run-status.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/runners/what-are-runners.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.