DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to cut sandbox start time with warm pools and snapshots with SPACE

Keep booted sandboxes ready or restore from a base snapshot to skip cold boots.

Who it is forAn operator running SPACE on Kubernetes or a single node who needs sandboxes to start quickly for interactive or agent workloads.

The problemCold boots of every new sandbox add latency to each create call.

The outcomeCreates reuse ready sandboxes from a warm pool or restore from a base snapshot, and you confirm the faster path with the operator CLI.

What you need first

  • A host that meets the prerequisites in docs/installation.md
  • Docker-compatible local setup for a Kind cluster, as described in docs/installation.md
  • Bash for installation and cluster diagnostics
  • Git and Python 3.11+ and mdBook 0.4.52 only if you build the docs locally

Steps

  1. Read [Warm pools](docs/warm-pools.md) and [Base snapshots](docs/base-snapshots.md) to choose the approach for your setup.
  2. Run space-admin-cli login to authenticate the operator CLI.
  3. Configure a warm pool or base snapshot as described in the guide.
  4. Create a sandbox and check that the create path matches the guide.

Prompt for your agent

In the perplexityai/SPACE repo, read docs/warm-pools.md and docs/base-snapshots.md, run `space-admin-cli login`, and configure a warm pool or base snapshot for <target node or cluster>. Report the configuration you applied and the create result. Verify that a new sandbox is created from the pool or snapshot as the guide describes.

Caveat. The README says base snapshots run on a single node, so the snapshot path does not apply to a multi-node setup as written.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page