Skip to content

armgit / cua

Public Imported from GitHub
0

Scale computer-use 2.0 with open-source drivers, cross-OS sandboxes, and benchmarks for training, evaluation, and data generation.

docs: add first Cloud Fleet tutorial (#3416)

r33drichards574570d19f91
diff --git a/docs/content/docs/concepts/how-sandboxes-work.mdx b/docs/content/docs/concepts/how-sandboxes-work.mdx
index 82eb6f7fa2..ac85f7cb7d 100644
--- a/docs/content/docs/concepts/how-sandboxes-work.mdx
+++ b/docs/content/docs/concepts/how-sandboxes-work.mdx
@@ -61,4 +61,4 @@ Each *fork* starts from the same snapshot but gets its own writable disk. Change
Local mode runs on the developer's hardware. Linux containers use Docker Desktop, macOS VMs use Lume, and VM backends can use QEMU or Hyper-V. Local execution depends on the machine's available CPU, memory, disk, and virtualization support. Select it with `local=True`.
-The sandbox still starts from an `Image`, exposes a code half and a GUI half, and can be ephemeral or persistent. Start with [Your first local sandbox](/tutorials/your-first-local-sandbox).
+The sandbox still starts from an `Image`, exposes a code half and a GUI half, and can be ephemeral or persistent. See [Choose and build a sandbox image](/how-to-guides/sandbox/images#how-a-linux-image-runs-locally) for local runtime details, or [Your first Cloud Fleet](/tutorials/your-first-cloud-fleet) for a guided hosted path.
diff --git a/docs/content/docs/concepts/what-is-computer-use.mdx b/docs/content/docs/concepts/what-is-computer-use.mdx
index a874d77712..f219ea4e65 100644
--- a/docs/content/docs/concepts/what-is-computer-use.mdx
+++ b/docs/content/docs/concepts/what-is-computer-use.mdx
@@ -103,6 +103,6 @@ Cua Driver exposes [permission policies](/concepts/how-permission-policies-work)
- **Learn it:** [Drive your first app with Cua Driver](/tutorials/drive-your-first-app) on an existing macOS, Windows, or Linux computer.
- **Use it:** [Install Cua Driver](/how-to-guides/driver/install) and connect it to an agent you already use.
- **Guide the agent:** [Install the Cua Driver agent skill](/how-to-guides/driver/install-agent-skill) to add cross-platform tool-selection and verification instructions.
-- **Isolate it:** [Start your first local sandbox](/tutorials/your-first-local-sandbox) for an isolated Linux computer.
+- **Isolate it:** [Create your first Cloud Fleet](/tutorials/your-first-cloud-fleet) for an isolated Linux computer.
- **Understand delivery:** [Browser targeting and background delivery](/concepts/browser-targeting-and-background-delivery) explains how browser tabs map to native windows.
- **Evaluate it:** [How we continuously validate Cua Driver](/concepts/how-cua-driver-is-validated) describes the evidence used to test desktop behavior.
diff --git a/docs/content/docs/how-to-guides/driver/connect-your-agent.mdx b/docs/content/docs/how-to-guides/driver/connect-your-agent.mdx
index 917a8daee1..ae60ac24d9 100644
--- a/docs/content/docs/how-to-guides/driver/connect-your-agent.mdx
+++ b/docs/content/docs/how-to-guides/driver/connect-your-agent.mdx
@@ -12,8 +12,8 @@ Driver integration](/concepts/choose-a-cua-driver-integration) to compare MCP,
the direct SDK, private workers, and app-hosted services.
<Callout type="info">
- This connects an agent to Cua Driver on the current machine. To create a disposable local desktop,
- use [Cua Sandbox](/tutorials/your-first-local-sandbox) instead.
+ This connects an agent to Cua Driver on the current machine. To create an isolated cloud desktop,
+ use [Cua Sandbox](/tutorials/your-first-cloud-fleet) instead.
</Callout>
## Before you start
diff --git a/docs/content/docs/how-to-guides/lume/gpu-passthrough.mdx b/docs/content/docs/how-to-guides/lume/gpu-passthrough.mdx
index 923aa609ab..e6fa0b47cb 100644
--- a/docs/content/docs/how-to-guides/lume/gpu-passthrough.mdx
+++ b/docs/content/docs/how-to-guides/lume/gpu-passthrough.mdx
@@ -11,7 +11,7 @@ This guide builds a small MIT-licensed shim and activates it for one process. Th
selected capability answers; it does not pass a physical GPU to the guest, patch the host, or change
the guest kernel. If you're looking for computer-use automation instead, start with
[Cua Driver](/tutorials/drive-your-first-app) or
-[Cua Sandbox](/tutorials/your-first-local-sandbox).
+[Cua Sandbox](/tutorials/your-first-cloud-fleet).
Read the [technical writeup](/blog/gpu-passthrough-macos-vms) for the mechanism, benchmark evidence,
and architectural context. Apple's [Metal capability tables](https://developer.apple.com/metal/capabilities/)
diff --git a/docs/content/docs/how-to-guides/lume/install-lume.mdx b/docs/content/docs/how-to-guides/lume/install-lume.mdx
index 4ced5ad5e8..9ebe8d1f5d 100644
--- a/docs/content/docs/how-to-guides/lume/install-lume.mdx
+++ b/docs/content/docs/how-to-guides/lume/install-lume.mdx
@@ -3,7 +3,7 @@ title: Install and run Lume
description: Install Lume, Cua's local Apple Silicon VM manager for macOS and Linux guests.
---
-Lume is Cua's local VM manager for Apple Silicon Macs. Use it when you want to create, run, or serve macOS and Linux VMs on your own machine. It can provide local VM substrate for Cua workflows, but the primary product choice is still [Cua Driver](/tutorials/drive-your-first-app) for an existing machine or [Cua Sandbox](/tutorials/your-first-local-sandbox) for a fresh isolated desktop.
+Lume is Cua's local VM manager for Apple Silicon Macs. Use it when you want to create, run, or serve macOS and Linux VMs on your own machine. It can provide local VM substrate for Cua workflows, but the primary product choice is still [Cua Driver](/tutorials/drive-your-first-app) for an existing machine or [Cua Sandbox](/tutorials/your-first-cloud-fleet) for a fresh isolated cloud desktop.
## Requirements
diff --git a/docs/content/docs/how-to-guides/recipes/automate-a-legacy-windows-app-behind-a-vpn.mdx b/docs/content/docs/how-to-guides/recipes/automate-a-legacy-windows-app-behind-a-vpn.mdx
index 8b79f3bd80..2897cff71b 100644
--- a/docs/content/docs/how-to-guides/recipes/automate-a-legacy-windows-app-behind-a-vpn.mdx
+++ b/docs/content/docs/how-to-guides/recipes/automate-a-legacy-windows-app-behind-a-vpn.mdx
@@ -79,6 +79,6 @@ When a desktop app has **no API** and only runs **behind the corporate VPN**, dr
## Scale this out
-When the same workflow must run concurrently, use local Cua Sandbox Windows VMs and cap concurrency to the resources available on the host. Start with [Run sandboxes in parallel](/how-to-guides/sandbox/scale-out) and [Your first local sandbox](/tutorials/your-first-local-sandbox).
+When the same workflow must run concurrently, use local Cua Sandbox Windows VMs and cap concurrency to the resources available on the host. Start with [Run sandboxes in parallel](/how-to-guides/sandbox/scale-out) and [Sandbox lifecycle](/how-to-guides/sandbox/lifecycle).
The driving logic stays the same. Each local Windows VM needs the VPN configuration and application included in its starting image. See [Choose and build a sandbox image](/how-to-guides/sandbox/images).
diff --git a/docs/content/docs/how-to-guides/recipes/export-contacts-overnight.mdx b/docs/content/docs/how-to-guides/recipes/export-contacts-overnight.mdx
index cf8542d46c..e0f5001033 100644
--- a/docs/content/docs/how-to-guides/recipes/export-contacts-overnight.mdx
+++ b/docs/content/docs/how-to-guides/recipes/export-contacts-overnight.mdx
@@ -67,4 +67,4 @@ Kick off the task before you leave. In the morning, open `~/contacts.csv` and sp
One logged-in browser profile handles one account at a time. To process several accounts, events, or platforms in parallel overnight, use one local Cua Sandbox per authenticated session and cap concurrency to the resources available on the host.
-Use [Run sandboxes in parallel](/how-to-guides/sandbox/scale-out) to run several local desktops, [Images](/how-to-guides/sandbox/images) to prepare their starting state, and [Your first local sandbox](/tutorials/your-first-local-sandbox) for the basic SDK lifecycle.
+Use [Run sandboxes in parallel](/how-to-guides/sandbox/scale-out) to run several local desktops, [Images](/how-to-guides/sandbox/images) to prepare their starting state, and [Sandbox lifecycle](/how-to-guides/sandbox/lifecycle) for the basic local SDK lifecycle.
diff --git a/docs/content/docs/how-to-guides/recipes/fill-a-form-from-a-local-file.mdx b/docs/content/docs/how-to-guides/recipes/fill-a-form-from-a-local-file.mdx
index 77a1381ca2..76fcdb79ee 100644
--- a/docs/content/docs/how-to-guides/recipes/fill-a-form-from-a-local-file.mdx
+++ b/docs/content/docs/how-to-guides/recipes/fill-a-form-from-a-local-file.mdx
@@ -57,4 +57,4 @@ Use this recipe when the data already lives on your machine, for example in a PD
One desktop fills one form at a time. To submit several forms in parallel, for example one per CSV row or one per applicant, run one local Cua Sandbox per job and cap concurrency to the resources available on the host.
-Use [Run sandboxes in parallel](/how-to-guides/sandbox/scale-out) to run the jobs concurrently. Use [Choose and build a sandbox image](/how-to-guides/sandbox/images) to stage the source files in an image or mount them into each sandbox. Use [Your first local sandbox](/tutorials/your-first-local-sandbox) for the basic SDK lifecycle.
+Use [Run sandboxes in parallel](/how-to-guides/sandbox/scale-out) to run the jobs concurrently. Use [Choose and build a sandbox image](/how-to-guides/sandbox/images) to stage the source files in an image or mount them into each sandbox. Use [Sandbox lifecycle](/how-to-guides/sandbox/lifecycle) for the basic local SDK lifecycle.
diff --git a/docs/content/docs/index.mdx b/docs/content/docs/index.mdx
index 8ad8ae750c..24f42d45d5 100644
--- a/docs/content/docs/index.mdx
+++ b/docs/content/docs/index.mdx
@@ -1,9 +1,9 @@
---
title: 'Cua documentation'
-description: 'Open-source computer-use automation for real machines and local isolated desktops.'
+description: 'Open-source computer-use automation for real machines and isolated desktops.'
---
-Cua is an open-source MIT-licensed platform ([github.com/trycua/cua](https://github.com/trycua/cua)) for **computer-use automation**: letting AI agents operate computers by clicking, typing, and reading the screen and accessibility tree. What we refer to as **Computer-Use 2.0** treats the GUI as one tool surface in an agent loop, alongside code, shell, files, and APIs. Use Cua Driver to drive a machine you already have, Cua Sandbox to start an isolated local desktop, or Cua-Bench to evaluate computer-use agents.
+Cua is an open-source MIT-licensed platform ([github.com/trycua/cua](https://github.com/trycua/cua)) for **computer-use automation**: letting AI agents operate computers by clicking, typing, and reading the screen and accessibility tree. What we refer to as **Computer-Use 2.0** treats the GUI as one tool surface in an agent loop, alongside code, shell, files, and APIs. Use Cua Driver to drive a machine you already have, Cua Sandbox to start an isolated desktop locally or in a Cloud Fleet, or Cua-Bench to evaluate computer-use agents.
For live service availability and incident updates, see [Cua Status](https://status.cua.ai).
@@ -15,9 +15,9 @@ import { Card, Cards } from 'fumadocs-ui/components/card';
already have without bringing them to the foreground or moving the real mouse. It speaks MCP
over stdio and is also a plain CLI.
</Card>
- <Card title="Start a local desktop — Cua Sandbox" href="/tutorials/your-first-local-sandbox">
- Start a disposable Linux desktop with Docker, or use a local VM runtime when you need a fresh,
- isolated computer on your own hardware.
+ <Card title="Start a cloud desktop — Cua Sandbox" href="/tutorials/your-first-cloud-fleet">
+ Provision a Cloud Fleet, claim a fresh isolated Linux desktop, run a useful operation, and
+ delete the cloud resources when you finish.
</Card>
<Card title="Evaluate agents with Cua-Bench" href="/concepts/what-is-cua-bench">
Define verifiable computer-use tasks, run agents across local or hosted environments, and score
@@ -65,4 +65,4 @@ How-to guides: recipes for a goal. Start with [How-to guides](/how-to-guides).
Reference: precise technical description. Start with [Reference](/reference).
-For existing apps and signed-in state, start with **Cua Driver**. For fresh isolated local desktops, start with **Cua Sandbox**. Lume is the local Apple Silicon VM substrate behind part of the stack.
+For existing apps and signed-in state, start with **Cua Driver**. For fresh isolated desktops, start with **Cua Sandbox** and choose local or Cloud Fleet execution. Lume is the local Apple Silicon VM substrate behind part of the stack.
diff --git a/docs/content/docs/tutorials/index.mdx b/docs/content/docs/tutorials/index.mdx
index d9c8dab499..11ac5bef5e 100644
--- a/docs/content/docs/tutorials/index.mdx
+++ b/docs/content/docs/tutorials/index.mdx
@@ -6,7 +6,7 @@ description: 'Learn Cua by following end-to-end builds.'
Get started with Cua by building something end to end. Each tutorial is *one happy path* you can follow from start to finish.
- [Drive your first app with Cua Driver](/tutorials/drive-your-first-app) - operate a native app in the background.
-- [Your first local sandbox](/tutorials/your-first-local-sandbox) - start a disposable Linux desktop with Docker.
+- [Your first Cloud Fleet](/tutorials/your-first-cloud-fleet) - provision an isolated Linux desktop in the cloud and clean it up.
- [Local macOS sandboxes with Lume](/tutorials/create-your-first-lume-vm) - install Lume and boot a vanilla Tahoe guest.
- [Build your first Cua-Bench task](/tutorials/your-first-cua-bench-task) - create and verify a simulated computer-use task.
diff --git a/docs/content/docs/tutorials/meta.json b/docs/content/docs/tutorials/meta.json
index c3e17df407..6ce0517ae9 100644
--- a/docs/content/docs/tutorials/meta.json
+++ b/docs/content/docs/tutorials/meta.json
@@ -4,7 +4,7 @@
"pages": [
"index",
"drive-your-first-app",
- "your-first-local-sandbox",
+ "your-first-cloud-fleet",
"create-your-first-lume-vm",
"your-first-cua-bench-task"
]
diff --git a/docs/content/docs/tutorials/your-first-cloud-fleet.mdx b/docs/content/docs/tutorials/your-first-cloud-fleet.mdx
new file mode 100644
index 0000000000..b4602c7f9a
--- /dev/null
+++ b/docs/content/docs/tutorials/your-first-cloud-fleet.mdx
@@ -0,0 +1,163 @@
+---
+title: Your first Cloud Fleet
+description: Provision a Cloud Fleet, claim an isolated Linux desktop, run a command, save a screenshot, and clean up the cloud resources.
+---
+
+import { Callout } from 'fumadocs-ui/components/callout';
+
+In this tutorial, you provision a one-sandbox **Cloud Fleet** on
+`run.cua.ai`, claim its Linux desktop, run `uname -a`, save a screenshot, and
+delete the Fleet. The Cua Sandbox SDK represents a Fleet as a `Pool` and an
+active desktop as a claim on that pool.
+
+<Callout type="info">
+ You need Python `>=3.11,<3.14`, [uv](https://docs.astral.sh/uv/), and Fleet
+ credentials with permission to manage sandbox pools.
+</Callout>
+
+<Callout type="warn">
+ A pool with `replicas=1` keeps one cloud sandbox warm until you delete the pool. Cloud resources
+ can incur usage charges. The script deletes the pool in a `finally` block; the cleanup section
+ also shows how to delete it after an interrupted run.
+</Callout>
+
+## 1. Authenticate with Fleet
+
+The SDK connects to `https://run.cua.ai` by default. Export a Fleet access
+token:
+
+```bash
+export FLEETS_TOKEN="<your-access-token>"
+```
+
+Or export OAuth client credentials:
+
+```bash
+export CUA_CLIENT_ID="<your-client-id>"
+export CUA_CLIENT_SECRET="<your-client-secret>"
+```
+
+`cua auth login` does not supply credentials to the Fleet SDK. See
+[Authentication](/reference/cua-cli/authentication#fleet-pools-need-their-own-credentials)
+for the supported Fleet credential paths.
+
+## 2. Choose a unique Fleet name
+
+Pool names are lowercase DNS labels and are globally unique across Cua
+accounts. Choose a name that identifies you or your team:
+
+```bash
+export CUA_POOL_NAME="<unique-lowercase-name>"
+```
+
+If the name belongs to another account, `Pool.apply()` returns
+`PoolAccessDeniedError`. Choose another name and run the script again.
+
+## 3. Create the Fleet script
+
+Save the following script as `first_cloud_fleet.py`:
+
+```python title="first_cloud_fleet.py"
+# /// script
+# requires-python = ">=3.11,<3.14"
+# dependencies = [
+# "cua-sandbox",
+# ]
+# ///
+
+import asyncio
+import os
+from pathlib import Path
+
+from cua_sandbox import Image, Pool
+
+
+IMAGE = (
+ "public.ecr.aws/k5j5w0x5/cua-ubuntu-24.04"
+ "@sha256:82702ebdd32d1f8fc05f2ea409a7c67d0ba9f8f8e4e9f1a89ce40989d5f4475d"
+)
+
+
+async def main() -> None:
+ pool_name = os.environ["CUA_POOL_NAME"]
+ print(f"Provisioning Cloud Fleet: {pool_name}")
+
+ pool = await Pool.apply(
+ Image.from_registry(IMAGE),
+ name=pool_name,
+ replicas=1,
+ cpu=4,
+ memory_mb=4096,
+ services={"server": 8000},
+ )
+
+ try:
+ async with pool.claim(
+ name="first-claim",
+ service="server",
+ time_to_start=900,
+ ) as sandbox:
+ print(f"Connected to sandbox: {sandbox.name}")
+
+ result = await sandbox.shell.run("uname -a")
+ if not result.success:
+ raise RuntimeError(result.stderr)
+ print(result.stdout.strip())
+
+ screenshot = Path("cloud-fleet.png")
+ screenshot.write_bytes(await sandbox.screenshot())
+ print(f"Screenshot saved to {screenshot.resolve()}")
+ finally:
+ print(f"Deleting Cloud Fleet: {pool_name}")
+ await pool.delete()
+
+
+asyncio.run(main())
+```
+
+## 4. Run it
+
+Run the script from the same directory. `uv` reads the inline metadata and
+installs `cua-sandbox` in an isolated environment:
+
+```bash
+uv run first_cloud_fleet.py
+```
+
+The first run can take several minutes while Fleet provisions the Linux
+sandbox. The script prints the sandbox name and Linux kernel information, then
+writes `cloud-fleet.png` in the current directory.
+
+When the claim block exits, the SDK releases the claimed sandbox. The `finally`
+block then deletes the pool and its template, so the warm cloud capacity does
+not remain running.
+
+## Clean up an interrupted run
+
+If the process is killed or loses connectivity after provisioning, the
+`finally` block might not reach Fleet. Keep `CUA_POOL_NAME` set and rerun the
+same script when connectivity returns:
+
+```bash
+uv run first_cloud_fleet.py
+```
+
+`Pool.apply()` reconciles the existing named pool instead of creating a second
+one. The script then uses the Fleet and reaches the same deletion path. Deleting
+the pool destroys its sandboxes and their state, so save any files you need
+before cleanup.
+
+## What you built
+
+`Pool.apply()` created or reconciled a named Fleet pool and its Linux sandbox
+template. `pool.claim()` reserved one sandbox and connected the SDK to its
+`server` service. The shell and screenshot calls operated on that cloud desktop,
+not on your local machine. Exiting the claim released the sandbox, and
+`pool.delete()` removed the Fleet resources.
+
+## Next steps
+
+- [Create a reusable sandbox pool with Python](/how-to-guides/sandbox/create-pool-with-python)
+- [Configure a sandbox pool with Terraform](/how-to-guides/sandbox/configure-pool-with-terraform)
+- [Expire pools and claims automatically](/how-to-guides/sandbox/expire-pools-and-claims)
+- [Sandbox SDK API reference](/reference/sandbox-sdk)
diff --git a/docs/content/docs/tutorials/your-first-local-sandbox.mdx b/docs/content/docs/tutorials/your-first-local-sandbox.mdx
deleted file mode 100644
index b4d0b7442a..0000000000
--- a/docs/content/docs/tutorials/your-first-local-sandbox.mdx
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: Your first local sandbox
-description: Create a local Linux sandbox with Docker, run one command, and save a screenshot.
----
-
-import { Callout } from 'fumadocs-ui/components/callout';
-
-In this tutorial, you create an *ephemeral* Linux sandbox on your machine, run `uname -a` inside it, touch the sandbox clipboard, and save a screenshot from the sandbox to your current directory.
-
-<Callout type="info">
- Prerequisites: Python 3.12 or 3.13 and Docker Desktop or Docker Engine.
-</Callout>
-
-<Callout type="error">
- **This tutorial does not currently work.** The published `trycua/cua-xfce:latest`
- runs computer-server bound to `127.0.0.1:8000` inside the container
- (`computer_server/cli.py:34` defaults `--host` to `127.0.0.1`), so Docker's
- published port mapping forwards to nothing and the script fails with
- `TimeoutError: Container <name> not ready after 120s`. The image needs rebuilding.
- In the meantime, drop `kind="container"` and use `Image.linux()`, which boots as a
- VM under QEMU and does not go through that image. It needs `qemu-system-x86_64`
- installed instead of Docker — see
- [Choose and build a sandbox image](/how-to-guides/sandbox/images#how-a-linux-image-runs-locally).
-</Callout>
-
-## Install the SDK
-
-Open a terminal and install the Python SDK:
-
-```bash
-pip install cua
-```
-
-## Create the script
-
-Create a file named `first_sandbox.py`:
-
-```python
-import asyncio
-from cua import Sandbox, Image
-
-async def main():
- async with Sandbox.ephemeral(
- Image.linux(kind="container"),
- local=True,
- ) as sb:
- result = await sb.shell.run("uname -a")
- print(result.stdout)
-
- await sb.clipboard.set("Hello from the sandbox clipboard")
- value = await sb.clipboard.get()
- print(value)
-
- screenshot = await sb.screenshot()
- with open("screenshot.png", "wb") as f:
- f.write(screenshot)
- print("Screenshot saved to screenshot.png")
-
-asyncio.run(main())
-```
-
-## Run it
-
-Run the script from the same directory:
-
-```bash
-python first_sandbox.py
-```
-
-You should see a Linux kernel string and the clipboard value printed in your terminal.
-
-You should also see a new file named `screenshot.png` in the current directory.
-
-## What just happened
-
-`Sandbox.ephemeral(..., local=True)` created a Linux desktop container through Docker on your machine. The script ran `uname -a` inside that container, printed the command output, changed and read the sandbox desktop clipboard, took a screenshot, and wrote it to `screenshot.png`.
-
-When the `async with` block exited, **the sandbox destroyed itself**. No cleanup is needed.
-
-## Next steps
-
-- [Manage sandbox lifecycle](/how-to-guides/sandbox/lifecycle)
-- [Choose and build a sandbox image](/how-to-guides/sandbox/images)
-- [Open an interactive sandbox shell](/how-to-guides/sandbox/interactive-shell)
-- [Sandbox SDK API reference](/reference/sandbox-sdk)
diff --git a/docs/content/docs/use-cua-with/anthropic.mdx b/docs/content/docs/use-cua-with/anthropic.mdx
index 44e423d5b5..bf587bb187 100644
--- a/docs/content/docs/use-cua-with/anthropic.mdx
+++ b/docs/content/docs/use-cua-with/anthropic.mdx
@@ -10,7 +10,7 @@ Anthropic provides the Claude model family. To give Claude access to a desktop,
| -------------------------------------- | ---------------------------------------------------------------------------------------------- |
| You use Claude Code | [Connect Claude Code to Cua Driver](/use-cua-with/claude-code) |
| You use another MCP client with Claude | [Use the generic MCP configuration](/how-to-guides/driver/connect-your-agent#generic-mcp-json) |
-| You want an isolated desktop | [Start a local sandbox](/tutorials/your-first-local-sandbox) |
+| You want an isolated desktop | [Start a Cloud Fleet](/tutorials/your-first-cloud-fleet) |
Claude Code can also act as the harness for a model served locally. That is a harness feature, not a direct connection between Cua Driver and Anthropic's API.
diff --git a/docs/next.config.mjs b/docs/next.config.mjs
index 98c9a2c28c..fd2a256d15 100644
--- a/docs/next.config.mjs
+++ b/docs/next.config.mjs
@@ -57,7 +57,12 @@ const config = {
},
{
source: '/tutorials/your-first-cloud-sandbox',
- destination: '/tutorials/your-first-local-sandbox',
+ destination: '/tutorials/your-first-cloud-fleet',
+ permanent: true,
+ },
+ {
+ source: '/tutorials/your-first-local-sandbox',
+ destination: '/tutorials/your-first-cloud-fleet',
permanent: true,
},
{