Prized Sandbox
Paseo hosts on Prized sandboxes. Stop pauses the sandbox with its memory and processes; Resume carries on from there.
该插件的概览尚未翻译为你的语言,因此以英文显示。
Prized Sandbox runs Paseo hosts on Prized sandboxes, cloud microVMs that pause with their memory. Each host is a sandbox with its own Paseo daemon and the Claude Code and Codex CLIs. You pair it with Paseo once and then create workspaces and agents on it like any other host. The plugin is published by Prized.
The plugin runs on your controller daemon and adds a Prized sandboxes item to the sidebar. Create host starts a sandbox from Prized's prized-agent-v1 template (Ubuntu 24.04, Node.js 22, Claude Code and Codex) in Oregon (us-west-2). It then installs a pinned Paseo CLI from npm into the sandbox's home directory, starts the daemon there and prepares a relay pairing link, which takes about 40 seconds. To pair, either use Copy pairing link and paste it into Hosts → Add host, or use Add to this daemon's hosts to save the host in the controller daemon's connected hosts. Agents, terminals and session history live in the sandbox. A host paired with its link keeps working while the controller is offline; one added to the daemon's hosts is reached through the controller. Create, stop, resume and delete need the controller online.
Stop pauses the sandbox, which keeps its memory and processes: the daemon, its terminals and the agent CLIs carry on from the same point on Resume, without restarting. A request to a model that was in flight when the host stopped may fail and need retrying. A stopped host bills storage only. Resume brings back the same daemon, which reconnects to the relay by itself, so the host needs no new pairing. A running sandbox is deleted when its running time ends: by default 24 hours, counted again from each resume, or on Prized's free credit 60 minutes in all, which a resume carries on. Stopped time never counts. The settings can set 1 hour to 7 days instead. Delete asks you to type the sandbox ID, then deletes the sandbox, its pairing link and its saved host.
Setup needs a Prized API key with Sandboxes: Write, entered in the plugin's settings or set as PRIZED_API_KEY in the controller daemon's environment. The key is stored in a file only the daemon's user can read, under the daemon's Paseo home, and is sent only to Prized's API (api.prized.dev) and to the sandbox's command endpoint (term.prized.dev). It never enters the sandbox. The settings can also hold an Anthropic and an OpenAI API key. They are set as environment variables on sandboxes created after you save them, so Claude Code and Codex start signed in. Prized stores them encrypted, but code running in the sandbox can read them. Without them, you sign an agent in from a terminal on the host. Size (2 vCPU and 4 GB up to 16 vCPU and 32 GB) and running time apply to hosts created after you change them. A key from another Prized workspace can't see a host's sandbox, so hosts made with another key show that and can't be changed until that key is back.
A new host has no repository: clone or create one in Paseo, under /home/prized/work. Private repositories need their own Git credentials inside the sandbox. Sandboxes have no root and no Docker, and nothing on the internet can reach them; the relay is the way in. A workspace on Prized's free credit runs sandboxes of up to 2 vCPU and 4 GB, for 60 minutes of running in all. Compute and storage are billed to your Prized workspace.

