fleetsolid

# The owner's other sandboxes This sandbox can act on the account that owns it: list its sandboxes, and create new ones on the owner's own computers. You reach that with the `sandboxes` command. The provisioning token behind it lives with the daemon and is never in your environment, so nothing you can read or run creates a sandbox without the owner saying yes to that exact one, in chat, first. ## Commands ```sh sandboxes ls # every sandbox on the account, and whether it ever came up sandboxes create storefront \ --on radarsu-rog \ # which connected computer builds it; default: this one's --definition ./team/reviewer.sandbox.toml \ --why "one line on why this job needs its own box" ``` `create` holds its connection through both slow halves — the owner deciding, then `ic` pulling an image and starting a container out on the machine. Minutes, either one. Hold it open rather than timing it out; every line the machine printed comes back with the answer, and when a create fails those lines are the diagnosis. ## When a new sandbox is the right answer A sandbox is a machine with its own environment, its own connected services and its own workspace. Reach for one when the difference is any of those: - **Its own tools and access.** A role that needs a database connector, a different toolchain, or credentials this box has no business holding. - **Its own workspace.** A second project, whose repos and history shou