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

# sandbox

The core of the CLI. Every per-device command takes a **selector**, resolved in order: exact uuid → uuid prefix → exact name → tag. An ambiguous selector (a tag matching several devices) errors and lists the matches.

## List

```bash
orchard sandbox list            # Rich table: name, uuid, provider, state, tag, node
orchard --json sandbox list     # machine-readable
```

## Inspect

```bash
orchard sandbox get my-pixel
```

## Create

```bash
orchard sandbox create ci-pixel \
  --platform android \
  --image "system-images;android-35;google_apis;x86_64" \
  --cpu 4 --memory 4096
```

Flags: `--platform ios|android`, `--cpu`, `--memory` (MiB), `--image`, `--node`.

## Start / stop / terminate

```bash
orchard sandbox start my-pixel
orchard sandbox stop  my-pixel
orchard sandbox rm    my-pixel        # terminate (deletes the disk); add --yes to skip the prompt
```

## Edit

```bash
orchard sandbox edit my-pixel --notes "under test" --cpu 8 --memory 8192
```

`--cpu`/`--memory` require the device stopped and are re-checked against your org quota; `--notes`, `--tag`, `--tag-color` work any time.

## Tag

A shortcut for the tag + colour that identify a device in the console:

```bash
orchard tag set my-pixel payments --color "#22c55e"
```

Tags are also selectors, so `orchard sandbox get payments` works once one device carries that tag (and a [tag-scoped key](/cli/access/keys.md) follows it automatically).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.orchard.airoverflow.com/cli/managing-sandboxes/sandbox.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.