Set up OpenSandbox on this VM by following the exe.dev recipe at https://exe.dev/deploy/opensandbox.md?via=terminal from top to bottom. The recipe's example VM name is my-opensandbox. This VM's name is the output of `hostname`: use it wherever the recipe writes my-opensandbox. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - The OpenSandbox server 1.2.1 with the Docker runtime, an API key, and a service that starts at boot - The API and every sandbox endpoint behind exe.dev login, reachable from scripts anywhere with a VM token - A first Python sandbox created, run, and deleted, in about a second once the image is pulled - A `desktop.py` script that opens an XFCE desktop in a sandbox in your browser tab, through noVNC - Sandboxes kept away from the API, from each other, and from the VM's exe.dev integrations - Claude Code and Codex on the VM using the server through OpenSandbox's MCP server Run "Set up by hand" from "On the VM" (skip creating the VM), then download hello.py and run it as in "Run your first sandbox", and check for its "hello from Python" line. Download desktop.py next to it, but don't run it: it starts a desktop for 30 minutes. Run the `exeuntu configure`, `claude mcp add` and `codex mcp add` commands from "Let an agent use it" and check that `claude mcp list` says Connected; skip the example prompts. Don't print the API key in your final message: say it is in ~/opensandbox/env. Leave INTEGRATIONS in firewall.sh at block unless the owner asks otherwise. Never make the VM public or point port 8000 at the API. Finish with the API's URL, using this VM's name, and the commands from "Use it from your computer". Finish with the URLs I should open.