> 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/guides/remote-cloud.md).

# Remote cloud sandboxes

Besides node-hosted devices, Orchard can drive **cloud** sandboxes on providers like e2b, daytona and modal. They are addressed by a numeric **record id**, not a uuid, and live under `orchard.remote`.

{% tabs %}
{% tab title="Python" %}

```python
orchard.remote.catalog()                      # which providers are configured
orchard.remote.add_credential("e2b", "e2b_xxx", label="team")

inst = orchard.remote.create("e2b", "scratch", image="base", ttl_minutes=60)
pk = inst["record_id"]
orchard.remote.start(pk); orchard.remote.stop(pk)
orchard.remote.upload(pk, "./data.json", "/root")
with orchard.remote.shell(pk) as sh:        # interactive shell
    for chunk in sh:
        print(chunk, end="")
orchard.remote.delete(pk)
```

{% endtab %}

{% tab title="TypeScript" %}

```ts
await orchard.remote.catalog();
await orchard.remote.addCredential("e2b", "e2b_xxx", { label: "team" });

const inst = await orchard.remote.create("e2b", "scratch", { image: "base", ttl_minutes: 60 });
const pk = (inst as any).record_id as number;
await orchard.remote.start(pk);
for await (const chunk of orchard.remote.shell(pk)) process.stdout.write(chunk);
await orchard.remote.delete(pk);
```

{% endtab %}
{% endtabs %}

Everything here is gated by the `platform.remote` feature on your org.


---

# 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/guides/remote-cloud.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.