diff --git a/content/manuals/agentic-platform/_index.md b/content/manuals/agentic-platform/_index.md index e26099a4816..9d91f38fae5 100644 --- a/content/manuals/agentic-platform/_index.md +++ b/content/manuals/agentic-platform/_index.md @@ -26,6 +26,10 @@ grid: description: Access, pause, resume, and delete your sandboxes. icon: command-line link: /agentic-platform/sandboxes/ + - title: Guides + description: Share an app, develop remotely, or continue local work in the cloud. + icon: command-line + link: /agentic-platform/guides/ - title: MCP description: Connect predefined or custom MCP servers. icon: cpu-chip diff --git a/content/manuals/agentic-platform/get-started.md b/content/manuals/agentic-platform/get-started.md index 7aef6e2af52..e139252d50b 100644 --- a/content/manuals/agentic-platform/get-started.md +++ b/content/manuals/agentic-platform/get-started.md @@ -11,8 +11,10 @@ aliases: Use a cloud sandbox to review a project with a coding agent or build and run an application from a shell, without setting up the project on your computer. -You can complete either workflow in the browser. An optional step shows how -to open the same project in VS Code or Cursor over SSH. +Both paths introduce the same cloud sandbox lifecycle: launch an environment, +run a task, save work, and pause or delete it. Complete either path in your +browser, then use the [guides](guides/_index.md) for sharing, remote development, +or moving local work to the cloud. ## Before you begin @@ -20,6 +22,9 @@ You need a personal Docker account with an active [Docker Agentic Platform subscription](signup.md#activate-cloud-access). Both workflows use a public sample project, so you don't need a GitHub token. +Review the compute price and timer before launching. Choose **Stop** as the +timeout action to keep files. Compute is billed while the sandbox runs; +closing the browser doesn't stop it. ## Choose a workflow @@ -73,8 +78,7 @@ Claude Code summarizes the project in the conversation and saves the review at `/home/agent/workspace/review.md`. You can ask follow-up questions or give it another task in the same session. -Continue to [keep your work](#keep-your-work), or -[open the project in your editor](#open-the-project-in-your-editor-optional). +Continue to [keep your work](#keep-your-work). ## Use a shell @@ -88,8 +92,9 @@ The Shell kit starts a Bash shell without an agent. 3. If saved secrets or a GitHub token are selected, deselect them for this walkthrough. You don't need MCP tools either. 4. In the network policy picker, select **Balanced** to permit access to - GitHub, Docker Hub, and npm. Keep the compute and timer defaults and select - **Run**. + GitHub, Docker Hub, and npm. Deselect **Open** if selected: combining it + with Balanced doesn't restrict Open's access. Review the compute price and + timer, choose **Stop** as the timeout action, and select **Run**. If you use a custom network policy, make sure it permits GitHub, Docker Hub, and npm. See [Network policies](policies.md). @@ -129,11 +134,13 @@ You should see the Welcome to Docker application. The application runs in the cloud sandbox, so you can try it without installing Docker or Node.js on your computer. -The generated URL is public. Close the port in **Connect** when you've finished -previewing the application. +The generated URL is public, and Docker account authentication doesn't protect +it. Use only non-sensitive data. Close the port in **Connect** when you've +finished previewing, then reload the URL to confirm access is withdrawn. +For a complete sharing workflow, including checking access from a separate +browser session, follow [Share an application](guides/share-app.md). -Continue to [keep your work](#keep-your-work), or -[open the project in your editor](#open-the-project-in-your-editor-optional). +Continue to [keep your work](#keep-your-work). ## Keep your work @@ -147,52 +154,9 @@ and push changes to a repository. Include a [GitHub credential](secrets.md#github-credential) when launching a sandbox that needs to push changes. -## Open the project in your editor (optional) - -Open the project in VS Code or Cursor over SSH to edit the application. Your -editor runs on your computer, while the files and terminal commands stay in -the cloud sandbox. - -1. Install the [Docker Sandboxes CLI](/manuals/ai/sandboxes/install.md), - version 0.45.0 or later. -2. In a terminal on your computer, sign in with the same Docker account you - used in the Console and configure cloud SSH access: - - ```console - $ sbx login - $ sbx --cloud setup ssh - $ sbx --cloud ls - ``` - -3. Find your sandbox in the list and copy its `sbx_`-prefixed ID. Test the - connection, replacing `` with that ID: - - ```console - $ ssh @sbx_cloud - ``` - - A successful connection opens a shell inside the cloud sandbox. Run `exit` - to return to your computer's terminal. -4. In VS Code, install the - [Remote - SSH extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-ssh). - In Cursor, install its Remote - SSH support. -5. Open your editor's Command Palette and run **Remote-SSH: Connect to Host**. - Enter `@sbx_cloud`, using the same ID as in the SSH command. -6. Open `/home/agent/workspace` in the remote window. Both workflows clone - the application into `project`. The coding agent also saves `review.md` - in the workspace. - -The first connection installs the editor's server inside the sandbox. - -If you followed the coding agent workflow, download the review run this command in a terminal on your computer: - -```console -$ sbx --cloud cp :/home/agent/workspace/review.md ./review.md -``` - ## Pause, keep running, or delete the sandbox -Closing the browser or disconnecting your editor leaves the sandbox running. +Closing the browser leaves the sandbox running. Commands and background processes can continue until you pause or delete the sandbox, or its timer expires. Compute is billed while the sandbox runs, even when no commands are running. @@ -209,27 +173,24 @@ Return to **Sandboxes** in the Console and choose what to do next: you want to keep first. Deletion removes files stored only in the sandbox. For more detail, see [Lifecycle actions](sandboxes.md#manage-the-lifecycle). + +## Sandbox options + +For launch settings, see [Kits](kits.md), [Secrets](secrets.md), +[Network policies](policies.md), and [MCP tools](mcp.md). For compute platforms +and timer actions, see [Sandboxes](sandboxes.md). Choose these settings before +launching: credentials, tools, network policies, and compute size can't be +changed afterward. + +## Next steps + To run a task from your own terminal, follow the [cloud CLI walkthrough](/manuals/ai/sandboxes/cloud/_index.md#get-started). For programmatic workflows, see the [Sandboxes API quickstart](/manuals/ai/sandboxes-api/get-started.md). -## Sandbox options +Continue with a targeted workflow: -After launch, you can't change the selected credentials, tools, network policies, -or compute size. Configure these options before selecting **Run**: - -| Option | What to choose | -| --- | --- | -| Sandbox name | Select **randomly** to enter a name, or keep the generated name. | -| Agent credentials | Add the API keys or tokens your kit needs. Saved credentials are reused by default; deselect optional credentials you don't want to include. See [Secrets](secrets.md). | -| GitHub token | Provide a token for Copilot or for cloning private repositories and pushing changes. Copilot uses the same token for both. Repository access is optional for other agents. See [GitHub credential](secrets.md#github-credential). | -| Network policies | Review the hosts and services the sandbox can reach. See [Network policies](policies.md). | -| MCP tools | Choose the servers your agent can use and authorize them if prompted. See [MCP](mcp.md). | -| Compute and platform | Choose a size based on the CPU and memory your task needs, from Micro for light tasks to XL for larger workloads. The picker shows each size's resources and hourly price. Under **Platform**, use **auto** or a platform supported by the kit's image. See [Sandbox platforms](sandboxes.md#choose-a-platform). | -| Timer | Under **Run for**, choose 1 to 24 hours. Under **When the time is up**, choose **Stop**, **Delete**, or **Restart** if offered. See [Lifecycle actions](sandboxes.md#manage-the-lifecycle). | - -The launcher remembers your policy selections from the previous launch in the -same browser. Policies marked **Always applied** are selected automatically. -Review the selected policies before launching. Selecting **Balanced** alongside -**Open** doesn't restrict Open's access; see [How policies combine](policies.md#how-policies-combine). +- [Share an application](guides/share-app.md) through a public URL. +- [Develop remotely](guides/remote-development.md) with VS Code or Cursor. +- [Continue local work in the cloud](guides/local-handoff.md) and retrieve the results. diff --git a/content/manuals/agentic-platform/guides/_index.md b/content/manuals/agentic-platform/guides/_index.md new file mode 100644 index 00000000000..7311776062c --- /dev/null +++ b/content/manuals/agentic-platform/guides/_index.md @@ -0,0 +1,16 @@ +--- +title: Docker Agentic Platform guides +linkTitle: Guides +description: Follow step-by-step workflows to share an application, develop remotely, or hand off a local task to a cloud sandbox. +keywords: docker agentic platform, cloud sandboxes, workflows, guides +weight: 25 +--- + +Choose a workflow to put a cloud sandbox to work: + +- [Share an application](share-app.md) through a public HTTPS URL, then withdraw access. +- [Develop remotely](remote-development.md) with VS Code or Cursor over SSH. +- [Continue local work in the cloud](local-handoff.md) and retrieve the results. + +For account setup, start with [Get started](/manuals/agentic-platform/get-started.md). +For command options, see [Use cloud sandboxes](/manuals/ai/sandboxes/cloud/usage.md). diff --git a/content/manuals/agentic-platform/guides/local-handoff.md b/content/manuals/agentic-platform/guides/local-handoff.md new file mode 100644 index 00000000000..757ba38b183 --- /dev/null +++ b/content/manuals/agentic-platform/guides/local-handoff.md @@ -0,0 +1,185 @@ +--- +title: Continue local work in the cloud +linkTitle: Local-to-cloud handoff +description: Prepare a bounded agent task in a local sandbox, move its filesystem to the cloud, and retrieve the results. +keywords: docker agentic platform, cloud sandboxes, workflows, local-to-cloud handoff +weight: 30 +--- + +Prepare a sample review locally, then let an agent finish it in the cloud while +your computer is disconnected. Retrieve the report before removing either +sandbox. Provisional duration: 25 minutes; this estimate needs measurement +during review. + +## Before you begin + +You need the [CLI and a supported local runtime](/manuals/ai/sandboxes/install.md), +version 0.45.0 or later, an active +[Docker Agentic Platform subscription](/manuals/agentic-platform/signup.md#activate-cloud-access), +and an Anthropic API key for Claude Code in the cloud. You can use a Claude +subscription locally, but cloud sandboxes require an API key. This guide uses +an API key in both environments. + +Docker bills cloud compute while the destination runs, even when disconnected. +Anthropic bills inference separately. The public sample needs no GitHub token. +Use the managed credential stores so keys stay out of the filesystem snapshot: + +```console +$ sbx login +$ sbx --cloud diagnose +$ sbx secret set anthropic +$ sbx --cloud secret set anthropic +``` + +Local and cloud secret stores are separate. See +[Cloud credentials](/manuals/ai/sandboxes/cloud/credentials.md). + +## Prepare files inside the local sandbox + +On your computer, create a mountless sandbox by omitting the workspace argument. +Clone the project inside it so the files transfer to the cloud. Directories +mounted from your computer and clone-mode volumes are outside the sandbox +filesystem and aren't included in a move: + +```console +$ sbx create --name handoff-local --cpus 2 --memory 4g claude +$ sbx policy allow network github.com:443 --sandbox handoff-local +$ sbx exec handoff-local git clone https://github.com/docker/welcome-to-docker.git /home/agent/workspace/project +$ sbx run --name handoff-local +``` + +Ask the local agent to prepare the task without carrying it out: + +```text +Read /home/agent/workspace/project. Don't modify it or install dependencies. +Record the full git HEAD revision and confirm the working tree is clean. +Write /home/agent/workspace/HANDOFF.md with that baseline, the project path, +and this remaining task: +Review package.json and the Dockerfile. Explain the build and startup commands, +identify the application's listening port, and recommend one small improvement +with a source path and reason. Don't modify the application or install anything. +Save the review to /home/agent/workspace/review.md. Include the baseline revision, +files read, and limitations. Don't claim to have run the application. +Don't start this review yet. +``` + +Exit the local agent when preparation is complete. Before snapshotting, remove +any credentials saved in filesystem files, including interactive sign-in files. +Managed secrets aren't copied, but ordinary credential files are. + +## Move the filesystem + +From your computer, run: + +```console +$ sbx move handoff-local --to cloud --ttl 2h --on-timeout stop +``` + +The move stops the local source for capture and creates a separate destination. +Use its printed `sbx_`-prefixed ID in place of ``. The move also creates +a template: the filesystem image used to create the destination, including +`HANDOFF.md`. It remains after you remove the sandbox. + +Cloud sandboxes support both `linux/amd64` and `linux/arm64`. The destination +matches your local sandbox's architecture; a move doesn't convert between them. + +The explicit timeout requests that the destination stop after two hours and +retain its files; the command +fails if stopping isn't supported. Don't substitute deletion without first +arranging to save your work. + +A move transfers a filesystem snapshot. Running processes, memory, open sockets, +workspace mounts, clone-mode volumes, and managed secrets don't transfer. +Local network rules don't transfer either. Published TCP sandbox ports can be +republished with cloud URLs; rejected ports produce warnings. See +[Move a sandbox](/manuals/ai/sandboxes/cloud/move.md) for transfer details. + +## Continue in the Console + +Open the [Console](https://agentic-platform.docker.com) and sign in with the +same Docker account you used for the CLI. Open **Sandboxes** and select the +destination using the ID printed by the move. Use its browser terminal to +continue the task; the local agent process wasn't transferred. + +Before starting work, confirm the destination's architecture, compute size, +and expiration match your expectations. Check that your cloud Anthropic +credential is set. This task needs no published ports; remove any unintended +exposure. Verify the +[cloud network policy](/manuals/ai/sandboxes/cloud/network-policy.md) permits +the model provider; local network rules don't transfer. + +In an additional shell, check the transferred handoff: + +```console +$ cat /home/agent/workspace/HANDOFF.md +``` + +Expect the recorded baseline, project path, and remaining task. Return to the +agent's terminal to restart the work. + +Give it this prompt: + +```text +Read /home/agent/workspace/HANDOFF.md. Confirm the baseline revision and clean +working tree before doing the remaining review. Stop and report a mismatch. +Complete only the recorded task and save /home/agent/workspace/review.md. +``` + +## Disconnect and retrieve the result + +Once the agent starts, close the browser tab to disconnect. The cloud agent +can continue while your computer is disconnected. The timer still applies; +no further work runs after the sandbox stops until you resume it. + +Return to **Sandboxes** in the Console and reopen the destination. If it is +paused, select **Restore to connect**. Resuming starts a fresh timer. Review +the agent's response in the browser terminal. + +> [!TIP] +> If the terminal appears stuck after reconnecting, try resizing it by resizing +> your browser window. This can make the agent interface redraw. + +When the report is ready, return to your computer's terminal and copy both files: + +```console +$ sbx --cloud ttl +$ sbx --cloud cp :/home/agent/workspace/review.md ./review.md +$ sbx --cloud cp :/home/agent/workspace/HANDOFF.md ./HANDOFF.md +``` + +Read the local copies. Expect the report to identify the recorded baseline, +explain the build and startup commands with file references, and state that the +application wasn't run. Compare it with the source rather than treating the +agent's claims as verified. Files don't synchronize after a move: copying these +results is what brings them back to your computer. + +## Clean up both sandboxes + +After verifying your saved files, remove the destination, its template, and the +local source. First inspect the destination to identify its backing template, +then list the templates. Find the matching entry, typically named +`moved-handoff-local-`, and use its ID as ``. Check the ID +against the inspected sandbox so you remove only this move's snapshot: + +```console +$ sbx --cloud inspect +$ sbx --cloud template ls +``` + +Delete the cloud sandbox before removing its backing template: + +```console +$ sbx --cloud rm +$ sbx --cloud template rm +$ sbx rm handoff-local +$ sbx --cloud ls +$ sbx --cloud template ls +$ sbx ls +``` + +Confirm both sandboxes and the template are absent. The template contains the +captured filesystem, so removing only the sandbox leaves that snapshot stored. +Removal deletes files stored only in those resources. +If retaining the cloud destination instead, stop it and confirm its state with +`sbx --cloud ls` to stop compute charges. Check the expiration again after any +resume. See [Stop or remove a sandbox](/manuals/ai/sandboxes/cloud/usage.md#stop-or-remove-a-sandbox). diff --git a/content/manuals/agentic-platform/guides/remote-development.md b/content/manuals/agentic-platform/guides/remote-development.md new file mode 100644 index 00000000000..2125d151b43 --- /dev/null +++ b/content/manuals/agentic-platform/guides/remote-development.md @@ -0,0 +1,126 @@ +--- +title: Develop remotely in a cloud sandbox +linkTitle: Remote development +description: Connect VS Code or Cursor to a cloud sandbox over SSH, edit and preview a sample, and save your work. +keywords: docker agentic platform, cloud sandboxes, workflows, remote development +weight: 20 +--- + +Keep project files and development tools in a cloud sandbox while using VS Code +or Cursor on your computer. Provisional duration: 25 minutes; this estimate needs +measurement during review. + +## Before you begin + +You need an active [Docker Agentic Platform subscription](/manuals/agentic-platform/signup.md#activate-cloud-access), +the [Docker Sandboxes CLI](/manuals/ai/sandboxes/install.md) version 0.45.0 or +later, an SSH client, and VS Code or Cursor. The public sample needs no GitHub +token or model API key. Use the same Docker account in the CLI and Console. + +Your editor window runs locally. Project files, terminal commands, and the +editor's remote server run inside the sandbox. Files don't sync to your computer. +Docker bills compute while the sandbox runs, even with the editor disconnected. + +## Create the remote project + +1. Open the [Console](https://agentic-platform.docker.com/) and select **+ New sandbox**. +2. Choose **shell**, deselect saved credentials and MCP tools, and select + **Open** so the editor can download its remote server and dependencies. + Open permits unrestricted outbound network access; use it here with the + public sample and no saved credentials. +3. Review the compute price and timer. Select **Stop** under **When the time is up** + to retain files, then select **Run**. +4. In the sandbox's browser terminal, clone the sample: + + ```console + $ git clone https://github.com/docker/welcome-to-docker.git project + ``` + +Expect `/home/agent/workspace/project` to contain the sample source and Dockerfile. +Local workspaces aren't mounted in the cloud sandbox. + +## Configure and test SSH + +In a terminal on your computer, run: + +```console +$ sbx login +$ sbx --cloud setup ssh +$ sbx --cloud ls +``` + +Copy the sandbox's `sbx_`-prefixed ID from the list, then test the connection: + +```console +$ ssh @sbx_cloud +$ ls /home/agent/workspace/project +$ exit +``` + +Expect a shell inside the sandbox and the project files. `exit` returns you to +your computer. Use the ID, rather than the sandbox's display name, for SSH. +See [Connect with SSH](/manuals/ai/sandboxes/cloud/usage.md#connect-with-ssh) +for proxy troubleshooting. + +## Connect your editor + +Choose the instructions for your editor: + +- In VS Code, install the + [Remote - SSH extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-ssh). + Open the Command Palette and run **Remote-SSH: Connect to Host**. +- In Cursor, install its Remote - SSH support. Open the Command Palette and run + **Remote-SSH: Connect to Host**. + +Enter `@sbx_cloud` using the ID you tested. In the remote window, +open `/home/agent/workspace/project`. The first connection installs the editor's +server inside the sandbox. Expect the editor to show a remote connection and +the same project files you listed over SSH. + +For local sandbox integration, see the separate +[VS Code](/manuals/ai/sandboxes/integrations/vscode.md) and +[Cursor](/manuals/ai/sandboxes/integrations/cursor.md) pages. + +## Edit and preview remotely + +In the remote editor, find a visible heading in the application's source, +change its text, and save the file. In the editor's remote terminal, build and run: + +```console +$ cd /home/agent/workspace/project +$ docker build -t welcome-to-docker . +$ docker run -d --name welcome-to-docker -p 3000:3000 welcome-to-docker +``` + +In the Console, select **Connect**, enter `3000` under **Connect via a Port**, +and select **Open Port**. Open the generated HTTPS URL and expect to see your +changed heading. This URL is public: Docker account authentication doesn't +protect it. Use non-sensitive data and application authentication for private +content. Close the port in **Connect** after checking the preview and reload +the URL to verify the application is no longer reachable. + +## Reconnect and keep your work + +Close the remote editor window, then connect again using the same host entry +and open the same directory. Expect your saved change to remain. Disconnecting +doesn't pause the sandbox. If the timer stopped it, resume it in the Console +before reconnecting; check the fresh timer and restart the workload if needed. + +From a terminal on your computer, copy the project out: + +```console +$ sbx --cloud cp :/home/agent/workspace/project ./cloud-project +``` + +Inspect the copied source and confirm that your edit is present. Alternatively, +commit and push to a repository you control. Configure a +[GitHub credential](/manuals/agentic-platform/secrets.md#github-credential) +with the required repository permissions before launching a sandbox for that workflow. + +## Clean up + +In **Sandboxes**, pause the sandbox and confirm its paused status to stop compute +charges and retain files. A resumed sandbox gets a fresh timer with the original +duration. Once you've verified your saved copy, delete the sandbox if you no +longer need it. Deletion removes the remote files and editor server. +See [Lifecycle actions](/manuals/agentic-platform/sandboxes.md#manage-the-lifecycle). diff --git a/content/manuals/agentic-platform/guides/share-app.md b/content/manuals/agentic-platform/guides/share-app.md new file mode 100644 index 00000000000..0ef793ed665 --- /dev/null +++ b/content/manuals/agentic-platform/guides/share-app.md @@ -0,0 +1,100 @@ +--- +title: Share an application from a cloud sandbox +linkTitle: Share an app +description: Build a public sample in a cloud sandbox, share its HTTPS URL, and close the port when you finish. +keywords: docker agentic platform, cloud sandboxes, workflows, share an app +weight: 10 +--- + +Run the Welcome to Docker application in a cloud sandbox and share a preview +without setting up the project on your computer. Provisional duration: 20 minutes; +this estimate needs measurement during review. + +## Before you begin + +You need a browser and an active +[Docker Agentic Platform subscription](/manuals/agentic-platform/signup.md#activate-cloud-access). +This public sample needs no GitHub token, model API key, or MCP tools. +Use non-sensitive data: the preview URL is public, and Docker account +authentication doesn't protect it. Add authentication to your application +before sharing private content or operations that change data. + +Docker bills compute while the sandbox runs, including when you disconnect. +Review the compute price and timer before launching. Choose **Stop** as the +timeout action to retain files; **Delete** removes them. A stopped application +can't serve visitors. See [Sandbox lifecycle](/manuals/agentic-platform/sandboxes.md#manage-the-lifecycle). + +## Launch a shell + +1. Open the [Console](https://agentic-platform.docker.com/) and select **+ New sandbox**. +2. Choose the **shell** kit. Deselect saved credentials and MCP tools. +3. Select **Balanced** for GitHub, Docker Hub, and npm access. Deselect **Open** + if selected; combining it with Balanced doesn't restrict Open's access. +4. Review the compute size, **Run for** duration, and **When the time is up** + action, then select **Run**. + +The browser terminal opens a Bash shell inside the sandbox. Local files aren't +mounted there. See [Network policies](/manuals/agentic-platform/policies.md) +if your account applies additional restrictions. + +## Build and run the sample + +In the sandbox terminal, clone the public project into the sandbox filesystem: + +```console +$ git clone https://github.com/docker/welcome-to-docker.git project +$ cd project +$ docker build -t welcome-to-docker . +$ docker run -d --name welcome-to-docker -p 3000:3000 welcome-to-docker +``` + +The build should finish successfully, and the last command should return a +container ID. Check the running container: + +```console +$ docker ps --filter name=welcome-to-docker +``` + +Expect the container to be running with port `3000` published in the sandbox. +This container port mapping alone doesn't create the public cloud URL. + +## Open and share the preview + +1. On the sandbox detail page, select **Connect**. +2. Under **Connect via a Port**, enter `3000` and select **Open Port**. +3. Open the generated HTTPS URL in a separate private browser session where + you aren't signed in to Docker. Expect the Welcome to Docker application. +4. Share the URL only after checking the page and confirming it contains no + private data. Anyone with the URL can access the exposed application. + +The service runs inside the sandbox. Closing your browser leaves it running +until you stop it or the timer action takes effect. + +## Withdraw access and save work + +Use the close action next to port `3000` in **Connect**. In the separate browser +session, reload the URL and confirm that the application is no longer reachable. +Don't share the URL further if withdrawal hasn't succeeded; stop the sandbox +and investigate before continuing. + +Stop the container in the sandbox terminal: + +```console +$ docker stop welcome-to-docker +``` + +The project remains at `/home/agent/workspace/project`. To keep changes outside +the sandbox, [copy the files](/manuals/ai/sandboxes/cloud/usage.md#transfer-files) +or push them to a repository you control using an appropriately scoped +[GitHub credential](/manuals/agentic-platform/secrets.md#github-credential). +Verify your saved copy before deleting the sandbox; files don't sync automatically. + +## Clean up + +In **Sandboxes**, pause the sandbox and confirm its paused status to stop compute +charges while retaining files. Resuming starts a fresh timer with the original +duration. Delete the sandbox after saving anything you need; deletion removes +files stored only there. + +For CLI port controls, timers, and file transfers, see +[Use cloud sandboxes](/manuals/ai/sandboxes/cloud/usage.md). diff --git a/content/manuals/ai/sandboxes/cloud/_index.md b/content/manuals/ai/sandboxes/cloud/_index.md index 3a397424aaf..d45faeb50c3 100644 --- a/content/manuals/ai/sandboxes/cloud/_index.md +++ b/content/manuals/ai/sandboxes/cloud/_index.md @@ -118,6 +118,9 @@ Removal deletes files stored only in the sandbox. For your own projects, see [Transfer files](usage.md#transfer-files) and [Authenticate cloud agents](credentials.md) before cloning private repositories. +For step-by-step sharing, remote development, and local handoff workflows, see +[Docker Agentic Platform guides](/manuals/agentic-platform/guides/_index.md). + ## Learn more - [Signup and billing](/manuals/agentic-platform/signup.md) covers activation