Sandbox templates - bead

Choose sandbox templates with the tools a new machine needs. Use a saved snapshot when you need prepared files and running memory.

You want	Use
A clean image with installed tools	A published disk template
Your own packages or application image	A custom template
Prepared files, processes, and memory	A ready snapshot
Per-machine values and credentials	Creation configuration

List available templates

bead templates
bead templates --tools

The catalog tells you what is published in your deployment. --tools describes exact pinned tool versions from build definitions; an inventory entry alone does not establish publication.

Choose a bead machine template

Template	Main tools
`base`	Lean Debian base and command-line utilities
`python`, `node`	Lean base with the named language runtime
`agents`	Codex, Claude Code, OpenCode, Pi, and browser/desktop testing tools
`computer`	Coding tools with a visible Linux desktop and Chromium
`devbox`	Coding tools with language, build, and container toolchains
`devbox-computer`	Devbox with the visible desktop
`openclaw`, `hermes`	Their native assistant application and dashboard

Select only names returned by your catalog. Devbox includes Docker Engine, Compose, and Buildx through the machine-local Unix socket.

Create from a template

bead create --template base --size small --kind temporary --timeout 300

Size and image are separate choices. Memory snapshots require their original CPU and memory bounds. Read machine sizes. Put slow installs in a reusable custom template or snapshot. Supply credentials at creation or prompt time through a credential profile.